Repository navigation
Skip CI for pull requests in the middle of a stack - #1401
Merged
Merged
Conversation
- Run tests, benchmarks and doc example tests only for the lowest unmerged pull request of a stack - Keep running them for pushes and for pull requests outside a stack
github-actions
Bot
requested review from
SooKim1110,
acktsap,
benelog,
jwChung and
mhyeon-lee
November 19, 2026 08:30
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
With GitHub's stacked pull requests, workflows run for every pull request in a stack, not only the one targeting
main. Each push to a stacked branch ran the tests and benchmarks of every pull request above it as well. This PR runs them only for the lowest unmerged pull request of a stack.(Optional): Description
Why the branch filter did not stop them
build.yml,benchmark.ymlanddoc-examples.ymlrun onpull_requestwithbranches: [ main, '[0-9]*.[0-9]*.x' ], so a pull request whose base is another feature branch was expected to be skipped.mainfor every pull request in the stack.fix/1390-object-immutable-containerandfix/restore-set-value-handling:auto assignranadded_to_stackin the timeline), andRun testsandRun benchmarkstarted for both at 07:33:24base_ref_force_pushedandhead_ref_force_pushedat 08:18)Change
static-analysisandtest(build.yml),jmh(benchmark.yml) andtest(doc-examples.yml) get the condition below.merge-resultsneedsjmh, so it is skipped with it.github.event.pull_request.stackexists only for a pull request in a stack, so the condition checks it fornullfirst.workflow_dispatchand pull requests outside a stack run as before.How Has This Been Tested?
actionlintreports nothing new for the three workflows (only the existing shellcheck notes onrun:scripts).Is the Document updated?
No documentation change is needed.