-
Notifications
You must be signed in to change notification settings - Fork 191
Add Rollup Procedure #268
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
Add Rollup Procedure #268
Conversation
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
Co-Authored-By: Yuki Okushi <huyuumi.dev@gmail.com>
Co-Authored-By: Yuki Okushi <huyuumi.dev@gmail.com>
@Centril Updated, could you re-review it? |
src/release/rollups.md
Outdated
PR, `@bors rollup-` to un-mark as a rollup). 'Performing a Rollup' then means | ||
collecting these changes into one PR and merging them all at once. The rollup | ||
command accepts three values `always`, `maybe`, and `never`. `@bors rollup` is | ||
equivalent to `rollup=always` (which will always put a PR in a rollup), and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: these commands, aside from rollup
(which will make the priority effectively negative) don't actually have any automatic effect like that; it is a suggestion to the person making a rollup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reworded to make that distinction more clear.
Thanks! |
This PR is a continuation of #87 with what @Centril has written about the current rollup procedure.
r? @Centril