Yicong-Huang opened a new issue, #4628: URL: https://github.com/apache/texera/issues/4628
### Task Summary `direct-backport-push.yml`'s `Discover direct backport targets` step considers a backport target green only when **every** matrix child has `conclusion === "success"`: ```js return targetJobs.length > 0 && targetJobs.every((job) => job.conclusion === "success"); ``` After #4622, `precheck` 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 a legitimately skipped stack appears as `conclusion: "skipped"` on the corresponding `backport (target) / frontend (...)` job. The discovery filter then rejects the target and the push is silently skipped. Example: PR #4622 itself merged with all `backport (release/v1.1.0-incubating) / *` jobs green except the frontend matrix child which was `skipped`. Run [25237976528](https://github.com/apache/texera/actions/runs/25237976528) discovered no green targets and skipped the push. The aggregator job in `required-checks.yml` already treats `skipped` as acceptable; the discovery filter should match. ### Priority P2 – Medium ### Task Type - [x] DevOps / Deployment -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
