Skip to content

pr-review: wait out the pre-approval Sentinel verdict, and show its gates as a count - #22452

Merged
CamSoper merged 1 commit into
masterfrom
CamSoper/pr-review-sentinel-wait
Oct 22, 2026
Merged

CamSoper merged 1 commit into
masterfrom
CamSoper/pr-review-sentinel-wait

Conversation

@CamSoper

Copy link
Copy Markdown
Contributor

Proposed changes

  • act.py Sentinel wait. After approving, the wait took the newest Sentinel verdict at its word, and at that moment it's the pre-approval one, which is red by construction. Six merges in one batch were refused on it and went green minutes later. The wait now ignores a red verdict older than the approval and polls up to 10 minutes for the re-evaluation.
  • Board chip. checks:sentinel:failing is gone. collect.py reads the gate table from the Sentinel's status comment (only when it was evaluated at the current head), and the row shows sentinel P/E -- gates passing out of the ones that apply -- with each gate and the Sentinel's reason for the failing ones in the tooltip.

make test-review-pipeline passes.

🤖 Generated with Claude Code

…ates as a count

act.py's post-approval wait took the newest Sentinel verdict at its word, and
right after an approval that verdict is the pre-approval one, red by
construction. Six merges were refused on it in one batch, every one green
minutes later. The wait now ignores a red verdict older than the approval and
polls up to 10 minutes for the re-evaluation.

The board's checks:sentinel:failing chip said nothing a row didn't already
say. collect.py now reads the gate table from the Sentinel's status comment
(when it was evaluated at this head), and the row shows sentinel:P/E -- gates
passing out of the ones that apply -- with each gate and the Sentinel's own
words for the failing ones in the tooltip.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@CamSoper
CamSoper merged commit ba466eb into master Oct 22, 2026
8 of 9 checks passed
@github-actions github-actions Bot added the review:triaging Claude Triage is currently classifying the PR label Oct 22, 2026
@CamSoper
CamSoper deleted the CamSoper/pr-review-sentinel-wait branch October 22, 2026 23:04
@CamSoper
CamSoper deployed to production October 22, 2026 23:04 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown
Contributor

Sentinel — merge gate status

2 of 5 gates need attention before this can merge.

Gate What it needs
🔴 G1 review-ran No current review for 2a150ed72 — comment /update-review <what changed> to refresh it, or /new-review for a fresh one.
➖ G2 findings-answered Doesn't apply to this PR: no review present — see G1.
🔴 G3 right-approver Needs an approval from anyone with write access to this repo — no qualifying human approval at this head (bot approvals count only on the automated lanes bot_approvers lists).
➖ G4 infra-evidence Doesn't apply to this PR: no changed path affects the deploy.
➖ G5 oversized-ack Doesn't apply to this PR: not oversized.

Break glass: a member of a routing team (.github/review-routing.yml teams:) can apply review:waived, which is logged.

Evaluated at head 2a150ed72.


Need help, or think a gate got it wrong? Ask in #docs on Slack.

@github-actions github-actions Bot added the domain:other PR touches no domain-specific path; reviewed under shared criteria only label Oct 22, 2026
@pulumi-bot
pulumi-bot requested a review from a team October 22, 2026 23:05
@github-actions github-actions Bot removed the review:triaging Claude Triage is currently classifying the PR label Oct 22, 2026
@pulumi-bot

Copy link
Copy Markdown
Collaborator

This branch had an error being deployed

1 failed and 1 active deployments
testing — 2a150ed7 Deployed Oct 22, 2026 by CamSoper via Do cleanup #14900
production — 2a150ed7 Deployed Oct 22, 2026 by CamSoper via Record review outcome #14900
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain:other PR touches no domain-specific path; reviewed under shared criteria only

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants