You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐛 Retire stale missing-required-check merge alerts on verified current-head evidence #16030
A real merge refusal for PR #16014 reported required changelog-fragment-guard missing. The check later succeeded on exact current head 0ab16c6, but the system banner remained visible. This proves stale alert state, not a bypassed CI gate or an infrastructure cause.
Root cause: periodic merge-failure alert revalidation has no missing-check resolution path. Repo/reason aggregation overwrites the originating PR, and an unrelated successful merge blanket-clears repository alerts.
Focused fix: preserve the existing aggregate banner identity while retaining per-PR observation tokens and originating heads; retire only positively resolved origins. Require current head/base consistency, current required producer metadata, complete bounded check/status pagination and successful exact-head evidence. API errors, incomplete/unknown metadata, pending/failed checks and concurrent new refusals retain the alert. Merging one PR must not hide another blocker.
Validation is CI-only per AGENTS. No check/protection weakening, rerun, deployment, configuration or permission changes.
Activity
🐛 fix: retire stale missing-check merge banners safely