ci: skip catalog shards for docs-only main pushes - #627
Merged
Conversation
kim-em
force-pushed
the
fix/skip-docs-only-main-catalog
branch
from
September 4, 2026 08:28
f90bb2e to
cae521e
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
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.
Main-branch pushes currently select the full catalog before inspecting changed paths, so a docs-only merge launches eight long-running catalog shards even though the pull request correctly skipped them.
This keeps full-catalog validation for every source, generated, script, test, workflow, action, manifest, template, or toolchain push (and for an initial push), while selecting no catalog work for documentation/misc-only pushes.
Validated locally with the selector test suite, Python syntax checks, actionlint, and the exact docs-only merge diff.