ci: documentation does not start CI at all - #234
Open
thedancingdeveloper wants to merge 1 commit into
Open
Conversation
The previous attempt kept the jobs and skipped their expensive steps. That cut the work but not the wait: two runners still started, and `main`'s protection required branches to be up to date, so every merge invalidated every other open branch. Each then needed a fresh run before it could merge, one at a time. A five-line documentation change cost twenty minutes. Two changes together: - `strict` is off on `main`'s required checks, so a merge no longer invalidates every other branch. This was the actual cost. - `paths-ignore` on both triggers, so a prose change starts no workflow at all. Safe only because of the first change: with `strict` on, a required check that never reports blocks the pull request permanently. The path list stays conservative. Anything not named still runs everything, so a new top-level file nobody thought about gets the gates rather than a free pass. Co-Authored-By: Claude Opus 5 (1M context) <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.
Follows #229, which cut the work but not the wait.
The actual cost was
strict.mainrequired branches to be up to date, so every merge invalidated every other open branch — each needing a fresh run before it could merge, serialised. That is where twenty minutes went, not the test suite.Two changes:
strict: falseonmain's required checks (already applied via the API)paths-ignoreon both triggers, so prose starts no workflow at allThe second is only safe because of the first: with
stricton, a required check that never reports blocks the PR permanently.Path list stays conservative — anything not named runs everything.
🤖 Generated with Claude Code