fix: docs only PR should skip code related gh actions#5765
Merged
Conversation
81e2908 to
d01a9a6
Compare
Contributor
There was a problem hiding this comment.
No issues were identified; the workflow update appears sound and aligned with the docs-only CI skip intent.
Status: No Issues Found | Risk: Low
Review Details
📁 7 files reviewed | 💬 0 comments
Instruction Files
└── .claude/
├── agents/
│ └── nango-docs-migrator.md
└── skills
marcindobry
approved these changes
Apr 1, 2026
d01a9a6 to
fff4fab
Compare
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.
looks like the behavior of the
paths-filteractions has changed when specifying more than one path. Bumping to v4 with explicitpredicate-quantifier: 'every'to bring back the expected behavior and skip code related actions when PR is only modifying docsThis update applies the filter-semantics fix consistently across CI workflows, while preserving expected execution behavior for non-PR contexts such as
merge_groupand direct pushes tomaster. It also distinguishes docs detection logic where needed so documentation-triggered validation behavior remains correct, not just docs-only skipping for code workflows.This summary was automatically generated by @propel-code-bot