Repository navigation
ci: gate the heavy jobs on which paths changed - #199
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.
Adds a
changesjob that diffs the PR against its base and sets two flags, then gates the heavy jobs on them. Skipped jobs count as passed inrequired-checks-passed, which still always runs, so the ruleset keeps working (a workflow-level paths filter would leave it never reporting).cmd/internal/data/scripts/go.modgo.sumcodecov.ymlmise.tomlsite/docs/only.github/workflows/ci.ymlzizmor always runs. Any failure computing the diff falls back to running everything. This PR edits ci.yml, so it runs the full set itself; the gating shows on the next PR. Checked with actionlint and zizmor, and the path regexes against sample file lists.