Which PRs show up here?
Every open, non-draft pull request that is approved by reviewers and
passing CI. Code review is done: this page tracks the final wait for a
release engineer to apply the project's
merge criteria.
When is a PR ready to merge?
When all three icons in Ready to merge? are green:
-
Conflict-free — applies cleanly.
-
Assignee approved — automatic for hotfixes,
unassigned PRs, and self-assignees.
-
Review window elapsed —
48 business hours,
4 for trivial PRs, none for
hotfixes.
Red means action is needed:
-
Merge conflict — rebase the PR branch onto the
latest target branch and resolve any conflicts.
-
Approval missing — at least one assignee must
approve.
A yellow clock shows the hours remaining
in the review window.
My PR has three green icons. Why hasn’t it been merged?
Release engineers process ready PRs several times a day, so it will
probably be merged within a few hours.
| hotfix |
Fixes a broken main branch; merged immediately. |
| trivial |
Small, low-risk change; the review window is 4 hours instead of 48 business hours. |
| override required |
A release engineer must override a failing or stuck required check to merge. |
| ci 42d |
The last full CI run is that many days old; CI should be re-run before merging. |
| review dismissed |
A “changes requested” review was dismissed by someone else; merits a second look. |
| dnm |
Do not merge. |
Release phase
During integration, features and fixes merge normally. During
feature
freeze, only bug fixes and release-blocking work are merged, and PRs
milestoned for the next release wait.