fix(ci): treat skipped backport jobs as green in Direct Backport Push#4629
Merged
Yicong-Huang merged 1 commit intoMay 2, 2026
Merged
Conversation
After apache#4622 the precheck step legitimately skips build stacks based on PR labels (e.g., a PR without the frontend label skips frontend). The backport caller propagates these toggles, so the corresponding backport (target) / frontend (...) job ends with conclusion=skipped. The discovery filter required every matching job to be success, so those legitimately-skipped jobs caused the whole target to be classified as not-green and push-backports was silently skipped. Match the Required Checks aggregator's logic by accepting both success and skipped. Closes apache#4628 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Yicong-Huang
added
the
release/v1.1.0-incubating
github-actions Bot
pushed a commit
that referenced
this pull request
May 2, 2026
…#4629) ### What changes were proposed in this PR? After #4622 the `precheck` step legitimately skips build stacks based on PR labels (e.g., a PR without the `frontend` label skips the frontend stack). The backport caller propagates these toggles, so the corresponding `backport (target) / frontend (...)` job ends with `conclusion: "skipped"`. `direct-backport-push.yml`'s discovery filter required **every** matching job to be `success`, so legitimately-skipped jobs caused the whole target to be classified as not-green and `push-backports` was silently skipped. Match the `Required Checks` aggregator's logic by accepting both `success` and `skipped`. ### Any related issues, documentation, discussions? Closes #4628. Triggered by run [25237976528](https://github.com/apache/texera/actions/runs/25237976528) for the merge of #4622. ### How was this PR tested? Single-line filter change; YAML parses locally. Will be exercised on the next merge of a PR with `release/*` labels and a partially-skipped build matrix. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> (backported from commit 8e40078)
SarahAsad23
pushed a commit
to SarahAsad23/texera
that referenced
this pull request
May 4, 2026
…apache#4629) ### What changes were proposed in this PR? After apache#4622 the `precheck` step legitimately skips build stacks based on PR labels (e.g., a PR without the `frontend` label skips the frontend stack). The backport caller propagates these toggles, so the corresponding `backport (target) / frontend (...)` job ends with `conclusion: "skipped"`. `direct-backport-push.yml`'s discovery filter required **every** matching job to be `success`, so legitimately-skipped jobs caused the whole target to be classified as not-green and `push-backports` was silently skipped. Match the `Required Checks` aggregator's logic by accepting both `success` and `skipped`. ### Any related issues, documentation, discussions? Closes apache#4628. Triggered by run [25237976528](https://github.com/apache/texera/actions/runs/25237976528) for the merge of apache#4622. ### How was this PR tested? Single-line filter change; YAML parses locally. Will be exercised on the next merge of a PR with `release/*` labels and a partially-skipped build matrix. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
What changes were proposed in this PR?
After #4622 the
precheckstep legitimately skips build stacks based on PR labels (e.g., a PR without thefrontendlabel skips the frontend stack). The backport caller propagates these toggles, so the correspondingbackport (target) / frontend (...)job ends withconclusion: "skipped".direct-backport-push.yml's discovery filter required every matching job to besuccess, so legitimately-skipped jobs caused the whole target to be classified as not-green andpush-backportswas silently skipped. Match theRequired Checksaggregator's logic by accepting bothsuccessandskipped.Any related issues, documentation, discussions?
Closes #4628. Triggered by run 25237976528 for the merge of #4622.
How was this PR tested?
Single-line filter change; YAML parses locally. Will be exercised on the next merge of a PR with
release/*labels and a partially-skipped build matrix.Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7)