fix(pr-pipeline): post resumed-branch statuses only when the branch is still at the checked tip #8574

Activity

1. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 20, 2026
2. github-actions commented on Oct 20, 2026

   

   github-actionsBot

   on Oct 20, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the report. As I read it, post-statuses.mjs posts pipeline/* statuses on a resumed branch's checked tip without first confirming the branch ref still points at that tip, unlike report-outcome.mjs. If the branch moves between run-checks and report-statuses, green statuses land on the old SHA. You note no merge gate reads pipeline/*, so the effect is misleading statuses rather than a gate bypass. The proposed fix is to read git/ref/heads/ before posting, post only when it equals checks.tip, and add a test that a moved branch posts nothing. The brief is clear and I found no duplicate issues. A maintainer will confirm the priority and work class.

   _{Automated triage. A maintainer reviews it.}
3. github-actions

   added

   priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 20, 2026
4. github-actions

   added the

   Bug

   issue type on Oct 20, 2026
5. kyle-sexton

   added

   status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.A maintainer confirmed the item is real and in scope; ready to be worked.

   on Oct 20, 2026
6. kyle-sexton

   closed this as completedin #8603on Oct 20, 2026