Standardize on a single ci status context - #1
Merged
Merged
Conversation
Adds the aggregate `ci` job the whole fleet now defines: it needs every other job in the workflow, always runs, and passes when each need either succeeded or was skipped. One context for the branch ruleset to require instead of one per job — and one that still reports on a PR where a path-filtered or conditional job correctly did not run. Replaces the hand-rolled auto-merge loop with a shim that enables GitHub's native auto-merge. The `automerge` label behaves exactly as before; the polling, the CI-result inspection and the branch lookup underneath it are gone, along with the free-plan constraint that made them necessary. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Rn19FnLSwT7aje6gTam39
`on: [push, pull_request]` triggers both events for a branch pushed to this repo, so each context — including the new `ci` gate — was reported twice per commit. Scope the push trigger to the default branch. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Rn19FnLSwT7aje6gTam39
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
1 participant
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.
Part of the fleet-wide standardization tracked in JumpstartLab/server-admin#124.
The
cijob. Aggregates every other job in the workflow. Nopaths:filter and noif:of its own, so it always runs and therefore always reports — a required context that can be skipped leaves its PR pending forever, with no timeout.if: always()so it still runs when a need failed; the step treats a skipped need as success and failure or cancelled as not. Both directions were proven on real runs in the pilot (JumpstartLab/manila#43).Auto-merge. The
automergelabel is unchanged as an interface. Underneath, the hand-rolled loop is replaced by a shim that turns on GitHub's native auto-merge and stops — GitHub holds the merge untilciis green. The shim refuses loudly if the base branch does not actually requireci, because enabling auto-merge on an ungated PR merges it immediately rather than waiting.Once this has landed everywhere, a single org-level ruleset requiring
cireplaces the fifteen per-repo rulesets.🤖 Generated with Claude Code
https://claude.ai/code/session_016Rn19FnLSwT7aje6gTam39