§4: gate the pull request - #1
Merged
Merged
Conversation
This repo deployed from main with nothing checking a change first, so the deploy was the first thing to find out. §4 puts the gate on the pull request; every other repo in the estate now requires a `ci` context, and this adds the one that was missing. The check runs the same build this repo already relies on rather than an invented approximation, and it fails if that build finds nothing to do — a gate that cannot fail is worse than no gate, because it reads as coverage. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0119vXMJC7FKdDTYJkLVLusg
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.
This repo deployed from main with nothing checking a change first, so the
deploy was the first thing to find out. §4 puts the gate on the pull request;
every other repo in the estate now requires a
cicontext, and this adds theone that was missing.
The check runs the same build this repo already relies on rather than an
invented approximation, and it fails if that build finds nothing to do — a gate
that cannot fail is worse than no gate, because it reads as coverage.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_0119vXMJC7FKdDTYJkLVLusg
🤖 Generated with Claude Code
https://claude.ai/code/session_0119vXMJC7FKdDTYJkLVLusg