Proposal
Enable GitHub Merge Queue on main. The current "approve, update branch, rerun CI, merge" loop needs a maintainer for every PR. The queue can run that loop on its own.
Why
Today each approved PR needs a maintainer to click "Update branch", wait for CI to rerun, then click "Merge". That costs maintainer time. It also lets stale-green PRs merge when main moves between the rerun and the click.
How it works
After approval, the PR enters the queue (manually, or via an auto-merge label). GitHub rebases it onto main, reruns the required checks, merges if green, drops it if not.
Rollout
- Branch protection on
main: enable "Require merge queue".
- Add a
merge_group: trigger to the required-check workflows (test.yml, docs.yml, test_notebook.yml, pypi.yml, install-conda-env.yml).
- Decide how Dependabot and the auto test-duration PR fit in.
I can draft the workflow edits in a follow-up PR if there is interest. Close this if I overlooked a prior discussion or there is a reason not to do it.
Proposal
Enable GitHub Merge Queue on
main. The current "approve, update branch, rerun CI, merge" loop needs a maintainer for every PR. The queue can run that loop on its own.Why
Today each approved PR needs a maintainer to click "Update branch", wait for CI to rerun, then click "Merge". That costs maintainer time. It also lets stale-green PRs merge when
mainmoves between the rerun and the click.How it works
After approval, the PR enters the queue (manually, or via an
auto-mergelabel). GitHub rebases it ontomain, reruns the required checks, merges if green, drops it if not.Rollout
main: enable "Require merge queue".merge_group:trigger to the required-check workflows (test.yml,docs.yml,test_notebook.yml,pypi.yml,install-conda-env.yml).I can draft the workflow edits in a follow-up PR if there is interest. Close this if I overlooked a prior discussion or there is a reason not to do it.