-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Forbid TODO markers on master branch #990
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
I tend to use TODO and FIXME exactly the other way around ;) |
yeah, me to, but rust-lang/rust prefers FIXME, and it makes sense to be consistent with it? |
The merge of #982 will have introduced another |
I don't plant to merge this until #988 is r+ed :) |
bors r+ |
990: Forbid TODO markers on master branch r=matklad a=matklad this makes TODO markers useful for things which you want to fix before sending a PR Co-authored-by: Aleksey Kladov <[email protected]>
A bit of git archeology revealed this: rust-lang/rust@fe77e96 Basically, there once was a policy in rust-lang to require issue numbers on FIXME comments, and to do was forbidden as a work-around for that. I guess it's a good idea to create issues for FIXMEs on a best-effort bases! |
Build failed |
bors r+ |
990: Forbid TODO markers on master branch r=matklad a=matklad this makes TODO markers useful for things which you want to fix before sending a PR Co-authored-by: Aleksey Kladov <[email protected]>
Build succeeded |
this makes TODO markers useful for things which you want to fix before sending a PR