ci: remove redundant push triggers and add check-main guard#24
Merged
ci: remove redundant push triggers and add check-main guard#24
Conversation
Branch protection uses strict=true, so CI already passes on PRs before merge. Remove push triggers from all CI/lint/CodeQL workflows and replace the CI gates in the release workflow with a check-main ancestry guard. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <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
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.
Summary
pushtriggers from check-dist, CI, CodeQL, and linter workflows — branch protectionstrict=truemakes these redundant since CI must pass on PRs before mergecheck-mainancestry guard that verifies the tag is onmainbefore buildingTest plan
🤖 Generated with Claude Code