-
Notifications
You must be signed in to change notification settings - Fork 697
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
[meta] Separate queue for high priority PRs? #10352
Labels
Comments
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
2 tasks
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 14, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
geekosaur
added a commit
to geekosaur/cabal
that referenced
this issue
Sep 18, 2024
This allows is to interrupt the merge queue for high priority PRs. It's using the "priority: high 🔥" label currently. Fixes: haskell#10352
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://docs.mergify.com/merge-queue/priority/. I expect this would be used when the "priority: high 🔥 " label is on a PR.
One possible use is that we might have needed to merge something to 3.14 while I was catching up on 3.12 backports. With a high priority queue, setting the priority label would send a 3.14 PR to the high priority queue, which would preempt any queued 3.12 backports and only resume them after the high priority PR(s) were merged.
The text was updated successfully, but these errors were encountered: