ci: skip steps that a change cannot affect #361
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!361
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/change-scope"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Contains the commit of #360. Merge #360 first; this PR then shows two commits.
Change
scripts/ci-scope.mjscompares the tested commit with its base (tree to tree) and gives two outputs:codeandopenspec.docs/,infrastructure/, root*.md,renovate.json5, agent config, non-CI workflowsopenspec/openspec validateRequired checks
All six jobs always run and always report. The
CI / *status contexts do not change. Only steps inside the jobs are skipped. The conditions fail open: a step is skipped only when the scope output is the literal stringfalse.Why it is safe to skip
infrastructure/are read by tests. #360 declares them as Turbo inputs. Each declared Turbo input counts as code, so there is one list.apps/,packages/ore2e/reads an inert directory without a Turbo input declaration..forgejo/workflows/ci.ymlandscripts/are not inert. This PR runs the full suite on itself.Verification
node --test, part ofpnpm test).ci.yml, new root file, zero base, unknown base. All gave the expected scope.The 14 narrowed runs used 63 of 950 minutes in the four gated jobs (6.6%). None of them had a real failure in a gated job.
The narrowed path cannot run in this PR, because this PR changes
ci.yml.🤖 Generated with Claude Code