Repository navigation
Run CI once per change: pull requests to main and pushes to main - #15
Merged
Merged
Conversation
Every pull request head ran the profile checks twice, once for the push to its branch and once for the pull_request event, spending the organisation's shared free Actions minutes twice for the same commit. Pushes now trigger CI only on main; pull requests still get their run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
What changed and why
The workflow triggered on
pushto every branch and onpull_requesttomain, so each PR head ran the checks twice on the organisation's shared free Actions minutes (about 180 left this month). Pushes now trigger only onmain; pull requests keep their run.Verification
python3 scripts/verify_profile.pyon this headThe operator wrote this PR, so it waits for the studio-reviewer (OPERATING-RULES §1). Merge with the account's no-reply author address, as #14.
AI involvement
Claude Code (Claude Fable 5.1), as the studio operator. Nothing further for a human to confirm.
Privacy impact
None: a workflow trigger.
Rollback
Revert the squash commit.
🤖 Generated with Claude Code