Yicong-Huang opened a new issue, #7021:
URL: https://github.com/apache/texera/issues/7021
### What happened?
The `Report backport decisions` step in
`.github/workflows/backport-auto-label.yml` is skipped on every run, so the
report comment and release-manager review request added in #6962 never fire.
Its guard is `if: ${{ steps.label.outputs.result }}`. The upstream `Label
fix PRs` step (`actions/github-script`, `result-encoding: json`) sets that
output with `core.setOutput("result", …)`, but the script has no `return`, so
github-script auto-writes the `result` output to the script's `undefined`
return value **after** the body runs, clobbering the explicit value.
`steps.label.outputs.result` therefore ends up empty and the guard is always
false.
Impact: a `fix:` PR whose modified files don't exist on a release branch
(e.g. #7013) is silently skipped with no comment nudging the author to check
and add the label by hand — real backports get dropped without a trace.
Expected: the report comment is posted and the branch's release manager is
requested for review.
Likely fix: rename the github-script output (e.g. `decisions`) so it doesn't
collide with github-script's reserved `result`, or drop `result-encoding: json`
and `return` the payload instead of `core.setOutput`.
### How to reproduce?
1. Open any `fix:` PR into `main`.
2. Open the **Backport Auto Label** run → the `Report backport decisions`
step shows `skipped`.
3. No `<!-- backport-auto-label-report -->` comment appears. Verified 0
report comments across #7013, #6983, #6958, #6908.
### Version/Branch
1.3.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
bfe2b535c
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
Run 30423275226 (PR #7013) — step "Report backport decisions": skipped
```
--
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]
