The GitHub Actions job "Required Checks" on texera.git/gh-readonly-queue/main/pr-7022-93c6307ebad8e68dc3b2186e2bb7a38501ebe102 has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: e66a5e435003db849cc53db71b64141448341da4 / Yicong Huang <[email protected]> fix(ci): rename backport auto-label output so its report step runs (#7022) ### What changes were proposed in this PR? The `Report backport decisions` step in `backport-auto-label.yml` is skipped on every run, so the report comment and release-manager review request added in #6962 never fire. Root cause: the step's guard reads `steps.label.outputs.result`. `actions/github-script` always writes the script's return value to an output named `result` after the body runs. The `Label fix PRs` script has no `return`, so that post-run write blanks out the explicit `core.setOutput("result", …)` — the guard is therefore always false. Fix: rename the output to `decisions` (github-script only reserves `result`), and update the guard and the `RESULT` env reference to match. No logic in either step changes. ### Any related issues, documentation, discussions? Closes #7021. ### How was this PR tested? - Confirmed the failure on run `30423275226` (PR #7013): the `Report backport decisions` step shows `skipped`. - Verified 0 `<!-- backport-auto-label-report -->` comments across #7013, #6983, #6958, #6908 (including PRs that were auto-labeled), confirming the step is systemically skipped. - Change is name-only; the report/review logic is untouched, so it runs unchanged once the guard sees the output. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.8) Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/30433111123 With regards, GitHub Actions via GitBox
