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.
The one exception is a hotfix: it
unbreaks main, so it is listed as soon as it is opened even when it is
not approved yet, is failing CI, or conflicts. The
Ready to merge? icons show what it still needs.
When is a PR ready to merge?
When all four icons in Ready to merge? are green:
-
Conflict-free — applies cleanly.
-
CI passing — also green when a release engineer
is expected to override the required checks.
-
Approved — reviewers signed off, and an assignee
did too; assignee approval is 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.
-
CI failing — fix the failures, or get the
override required
label.
-
Approval missing — the PR is not approved yet,
or no assignee has approved it.
A yellow clock shows the hours remaining
in the review window.
A yellow arrow means CI is still running.
My PR has four 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. |
| held by freeze |
Milestoned after the release in progress; waits for the feature freeze to end. |
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 a later release wait. They are hidden by default; uncheck
Hide PRs held by the feature freeze to list them anyway, marked
held by freeze.