Repository navigation
fix(ci): select affected components on main pushes - #224
Merged
Merged
Conversation
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.
Every push to main currently reruns full validation after the PR has passed. Use the same affected-component selection on main so documentation, version-only, and small tooling changes also use the shorter validation path after merging.
Select the range from the push event's pre-push SHA through the new tip, covering every commit in a normal push. Fall back to full validation when that base is missing, zero, unavailable, or not an ancestor. Pass the verified comparison base to metadata validation so version/changelog checks still apply. PR merge-base selection remains intact; nightly, manual, and release-tag validation stays full.
Validation: 55 policy tests passed, including multi-commit pushes, documentation/version fast paths, missing history, rollback/divergent pushes, metadata-base output, and required PR bases. Actionlint, shellcheck, and workspace metadata checks passed. This CI policy change selects full GitHub validation under the conservative selection rules.