-
Notifications
You must be signed in to change notification settings - Fork 628
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
Warn when PR is opened for 0.3/0.1 branch #2813
Comments
I think having explicit mention of it in CONTRIBUTING.md (or even any documentation about the branching/backporting policy at all) would be a good start. I explicitly looked for some, didn't find any, found that HEAD pointed at 0.4, and figured I should target my bugfix to the release branch. In other words, it wasn't exactly an accident: it was my genuine best guess at how to get a bugfix merged into a previous release line in the absence of documentation, given that I was uncertain that a fix to master would get cherry-picked to a release branch. |
cc @Kobzol: Are there any options for doing this in rust-lang/team or somewhere? |
This would help avoid problems like #2801 (comment).
rust-lang/rust already has a mechanism for this (rust-lang/rust#118607 (comment)), but I don't know how to enable it for this repo.
The text was updated successfully, but these errors were encountered: