ci: fix required-check deadlock (pass-through shim)#26
Merged
Conversation
Fix a required-status-check deadlock by converting the path-filtered required job to a **pass-through shim** (same pattern as echidna#256). ## Why This job is a **required** status check but its workflow is path-filtered on `pull_request`, so it never runs (never reports) on PRs that don't touch those paths — branch protection then waits forever and the PR can't merge via normal flow. ## Fix - Drop the `pull_request` paths-filter so the job **always runs** (the required check always reports). - A `Detect relevant changes` step reads the PR's changed files via the GitHub API and gates the heavy steps — real work runs only when the relevant sources change; otherwise it passes through in seconds. - `push` stays scoped to the default branch + paths (post-merge behaviour unchanged); job names preserved so the required contexts still match. Identified by the 2026-06-14 estate required-check deadlock audit (`dev-notes/audits/`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
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.
What
Fix a required-status-check deadlock by converting the path-filtered required job to a pass-through shim (same pattern as echidna#256).
Why
This job is a required status check but its workflow is path-filtered on
pull_request, so it never runs (never reports) on PRs that don't touch those paths — branch protection then waits forever and the PR can't merge via normal flow.Fix
pull_requestpaths-filter so the job always runs (the required check always reports).Detect relevant changesstep reads the PR's changed files via the GitHub API and gates the heavy steps — real work runs only when the relevant sources change; otherwise it passes through in seconds.pushstays scoped to the default branch + paths (post-merge behaviour unchanged); job names preserved so the required contexts still match.Identified by the 2026-06-14 estate required-check deadlock audit (
dev-notes/audits/).🤖 Generated with Claude Code