Repository navigation
ci: skip verify and docs build on PRs that don't touch their inputs - #41
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.
Follow-up to the Mac mini CI speedup review. Generated with the Codex CLI and reviewed.
A small
changesjob (dorny/paths-filter, pinned SHA, on the minis) runs on PRs only; pushes, manual runs and other events always run everything. A job skipped byif:reports as successful, so required checks keep reporting and merges never block.Tests / verify(required): skipped on prose-only PRs. Package README/CHANGELOG/LICENSE and docs Markdown/MDX still run it, since they are packed or built/typechecked.Documentation / build(required): runs only whenapps/docs/**,packages/haptic/**,vendor/**, package manifests/lockfiles,.npmrc, the Playwright browsers action or the workflow change. Deploy and live smoke onmainare unchanged.verifyandbuildare unchanged, so the required checks still match.All jobs stay on
[self-hosted, macOS, ARM64]with the fork-PR guard.