-
Notifications
You must be signed in to change notification settings - Fork 61
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
Conversation
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? |
Yep! Thanks @withoutboats for pushing on this! |
@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? |
also as you can probably tell i am irresponsible and just pushed without testing because i didnt want to set up a db |
@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 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. |
Done :) Some other thoughts though:
|
Sounds great. Also see #89 (comment) for some previous discussion of a wider variety of rust-lang/rust commands and multiple FCP timeframes. |
thanks! |
* Add 'entering-final-coment-period' label. * Add comment type to RfcBotComment * Type error. * Fix ref business. Former-commit-id: e717688
No description provided.