-
Notifications
You must be signed in to change notification settings - Fork 25
rulesets/nixpkgs: enable merge queue on secondary development branches #183
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
rulesets/nixpkgs: enable merge queue on secondary development branches #183
Conversation
This enables Merge Queues on secondary development branches like staging and haskell-updates as well. These branches still need to be pushed to manually for the periodic merges, both automated by CI and manually by committers. Compared to the ruleset for merge queues on the primary development branches, this `always` allows bypassing. Since the number of merges on these branches is much lower, an occasional bypassing of the queue for the periodic merges is not a problem, at least resource-wise. We will still want to eventually implement a PR-based workflow for periodic merges to make sure these never break the branch.
8f31726 to
84b4994
Compare
|
Thanks for the quick look. This is already implemented, but merge is blocked because I fixed the |
|
Thanks! |
| "include": [ | ||
| "refs/heads/haskell-updates", | ||
| "refs/heads/staging", | ||
| "refs/heads/staging-next", |
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.
Should staging-nixos be added here?
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.
Yes. Could you open a PR?
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.
This enables Merge Queues on secondary development branches like staging and haskell-updates as well.
These branches still need to be pushed to manually for the periodic merges, both automated by CI and manually by committers. Compared to the ruleset for merge queues on the primary development branches, this
alwaysallows bypassing. Since the number of merges on these branches is much lower, an occasional bypassing of the queue for the periodic merges is not a problem, at least resource-wise.We will still want to eventually implement a PR-based workflow for periodic merges to make sure these never break the branch.
Although not the primary motivation, this will also resolve #135.
cc @NixOS/nixpkgs-ci