Skip to content

Add 'proposed-final-coment-period' label. #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 23, 2017

Conversation

withoutboats
Copy link
Contributor

No description provided.

@anp
Copy link
Member

anp commented Jun 22, 2017

Awesome! Unfortunately CI is failing on a reference/value type mismatch: https://travis-ci.org/dikaiosune/rust-dashboard/jobs/245632172#L804 (can't wait for match ergonomics RFC to land!!!!)

cc @aturon -- I'm assuming that you're good with this and that someone will make sure to create this label on the rust-lang org's repos?

@aturon
Copy link
Member

aturon commented Jun 22, 2017

Yep! Thanks @withoutboats for pushing on this!

@withoutboats
Copy link
Contributor Author

@dikaiosune ahh I've created this already on RFCs, forgot we used this on other repos? What repos does the label need to exist on?

@withoutboats
Copy link
Contributor Author

also as you can probably tell i am irresponsible and just pushed without testing because i didnt want to set up a db

@anp
Copy link
Member

anp commented Jun 22, 2017

@withoutboats mostly just on rust-lang/rust, although it will technically work on any rust-lang, rust-lang-nursery or rust-lang-deprecated repo. Might want to just ignore the error case rather than ?ing when applying the label so that we don't early return if someone proposes FCP on a repo without the label?

Totally understand on the database. It was super nifty to use when I was building this out and was the only maintainer, but I probably need to explicitly lay out the schema and just add a test that ensures it matches for CI to run. Would make it easier to contribute small, obvious fixes if the db wasn't required to build.

@withoutboats withoutboats changed the title Add 'entering-final-coment-period' label. Add 'proposed-final-coment-period' label. Jun 22, 2017
@withoutboats
Copy link
Contributor Author

withoutboats commented Jun 22, 2017

Done :) Some other thoughts though:

  • When entering actual FCP should probably remove the label. I think we can deploy adding the label without that, though, I'll just follow up on it eventually. Currently there's not a nice label removal abstraction in github::Client.
  • I'm thinking about adding a set of disposition tags which it will also set, so that its very easy to see what we're considering doing with this proposal. (It might also be worth adding additional dispositions for the rust repo, right now we just use "merge" as a synonym for "positive inclination").

@anp
Copy link
Member

anp commented Jun 22, 2017

Sounds great. Also see #89 (comment) for some previous discussion of a wider variety of rust-lang/rust commands and multiple FCP timeframes.

@anp
Copy link
Member

anp commented Jun 23, 2017

@anp anp merged commit e717688 into rust-lang:master Jun 23, 2017
@anp
Copy link
Member

anp commented Jun 23, 2017

thanks!

anoadragon453 pushed a commit to matrix-org/mscbot that referenced this pull request Jul 6, 2018
* Add 'entering-final-coment-period' label.

* Add comment type to RfcBotComment

* Type error.

* Fix ref business.


Former-commit-id: e717688
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants