ci: skip workflows for PRs tagged [skip ci] or labeled skip-ci#4291
Merged
Conversation
Add a job-level if: gate to the entry job of every PR-triggered workflow. When the PR title contains [skip ci], the entry job is skipped and downstream jobs cascade-skip via needs. Push triggers are unaffected since GitHub natively honors [skip ci] in commit messages for push events.
comphead
reviewed
May 11, 2026
Contributor
comphead
left a comment
comphead
left a comment
There was a problem hiding this comment.
Thanks @andygrove wondering if we can use a github tag instead of title?
Member
Author
Only committers have the ability to add labels but anyone can edit the title of their own PRs |
Member
Author
I added the option to use either approach |
andygrove
changed the title
[skip ci] or labeled skip-ci
Contributor
Actually this looks dangerous, we can possibly merge non verified PR
|
Member
Author
PR to revert #4301 |
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
2 participants
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.
Which issue does this PR close?
N/A.
Rationale for this change
Allow contributors to opt out of CI runs on work-in-progress PRs by adding
[skip ci]to the PR title. Saves runner minutes for draft iterations where CI feedback is not yet needed. Push events onmainare unaffected; GitHub already honors[skip ci]in commit messages for push triggers.What changes are included in this PR?
Adds a job-level
if:gate to the entry job of every PR-triggered workflow:Downstream jobs cascade-skip via their
needs:chain. Affected workflows:codeql,iceberg_spark_test,miri,pr_benchmark_check,pr_build_linux,pr_build_macos,pr_markdown_format,pr_missing_suites,pr_rat_check,pr_title_check,spark_sql_test,validate_workflows.Note: removing
[skip ci]from the title alone will not re-trigger workflows. A new push (or close/reopen) is required. This avoids re-triggering on every description edit, which would happen ifeditedwere added topull_request.types.How are these changes tested?
YAML validity confirmed locally. Behavior verifiable by opening a follow-up PR with
[skip ci]in the title and observing that all CI jobs are skipped.