Make repository validation PR-only (#538) - #539
Merged
Merged
Conversation
Drop validate.yml's push-to-main trigger so a merge no longer re-runs the FULL suite and cross-platform Skill-tree builds; pushes to main stay reserved for release-publish.yml. Update the docs that promised FULL on every push, and pin the pull_request-only trigger in the routing test. Co-Authored-By: Claude Opus 5.5 <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.
Fixes #538
What
validate.ymlnow triggers onpull_requestonly. Thepush: branches: [main]trigger is removed, so a merge no longer re-runs the FULL suite, the Skill-tree builds, spec validation, and the shell/PowerShell parity jobs. PR routing (FAST/FULL) and all validation jobs are unchanged. The route step still resolves any non-PR event to FULL, as a defensive fallback.release-publish.ymlis untouched: it still runs onpushtomain, with its own build, provenance, distribution, tag, and release verification.policies/validation-and-clean-exit.md("Routed CI tests") now states that the pre-merge boundary is PR-only. It also drops the "every push tomainruns FULL" safety net: a missed allowlist consumer now surfaces on the next PR that routes FULL. README and.github/AUTOMATION.mdare updated to match.test_ci_test_routing.pynow asserts the trigger set is exactly{pull_request}.CHANGELOG.md(seedocs/RELEASE.md)Validation
tests/policy/governance: OK. Markdown link validation: OK.Release publish, notValidate repository.Review
None yet.
🤖 Generated with Claude Code