ci(e2e): skip e2e on docs and version-bump-only PRs#3875
Merged
Conversation
elitegreg
approved these changes
Jun 10, 2026
elitegreg
left a comment
Contributor
There was a problem hiding this comment.
How about any *.md file?
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.
Summary of Changes
setupjob inspects the PR's changed files via the API. A PR qualifies only if every file is either markdown (*.md, any path; renames/copies must come from markdown too, since a rename also deletes the source path) orCargo.toml/Cargo.lockwith diffs touching nothing butversion = "..."lines, with the two Cargo files changing together. A dependency bump fails the check —cargo updatechanges Cargo.lock checksum/source lines, an inline requirement change in Cargo.toml doesn't match the version-line shape, and a requirement change that leaves the lock untouched fails the pairing rule — as does any code file or an API-truncated patch. All of those fall through to a normal e2e run. Markdown is verified inert: no.mdfiles are used as test fixtures, embedded viainclude_str!, or read by e2e code.e2e (shard 1-5)/shard-e2e (shard 1-4)contexts as successful on the PR head via the checks API (same pattern the trusted fork-PR flow already uses), so branch protection doesn't block the merge.pull_requestevents; fork PRs, pushes to main/hotfix, and trustedworkflow_dispatchruns are unaffected. Any gate error fails open to running e2e.Diff Breakdown
Workflow-only change; the same gate logic is added to both e2e workflows.
Key files (click to expand)
.github/workflows/e2e.yml— skip-gate step + early exit in the existingrun-e2egate; reportse2e (shard 1-5)checks when skipping.github/workflows/shreds-e2e.yml— same gate; reportsshard-e2e (shard 1-4)checks when skippingTesting Verification
cargo update-shaped Cargo.lock diff (checksum lines); dependency requirement change in Cargo.toml, both inline and multi-line-table form with the lock untouched; lock-only version-line change..rsto.md, and a Cargo.lock with an API-omitted patch all run e2e.actionlintpasses on both workflows.