Repository navigation
fix(ops): read the CI gate from main-branch runs - #206
Closed
harlan-github-agent[bot] wants to merge 1 commit into
Closed
harlan-github-agent[bot] wants to merge 1 commit into
harlan-github-agent[bot] wants to merge 1 commit into
Conversation
…e page mixed pull-request runs in newest-first, so ten red PR Test runs archived a broken main gate while main was green and deployed.
Contributor
Author
🤖 CLOSED
GitHub closed this pull request. No further automated Review will run. |
Collaborator
|
Closed as a duplicate of #199, which scopes both CI reads to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Closes #205
❓ Type of change
📚 Description
On 2026-09-08 the daily check-in archived the main Test gate as broken while main was green and deployed. The per-workflow read asked
gh run list --workflow <name>with no branch filter, so pull-request runs filled the page newest-first and ten red runs on one PR branch read as a failed main gate.The page the gate reads is now scoped to
--branch main, which is the question the gate actually answers: is main healthy. The regression case builds the real per-workflow command, and a fakeghapplies--branchserver-side exactly like the CLI. Without the flag, the same history reports:With the flag, it reads through to main's green run and reports
success.One tradeoff a reviewer should see: the deploy workflow is triggered by
workflow_runfrom every branch, and its guard skips itself offmain. Those skipped PR-branch rows no longer reach the sample at all, so the head page spends its ten rows on real main runs. The deeper-sample fallback from the 2026-09-02 skipped-guard fix is untouched for anything that still skips on main.