The GitHub Actions job "Backport Auto Label" on texera.git/ci/backport-auto-label-report has succeeded. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 2ef56e040840e3e5d7f073b6f09fe085cd2a6efa / Yicong Huang <[email protected]> ci: report backport auto-label decisions on the PR (#6961) The auto-label workflow decides per release branch whether to add a release/* label, but its skips were only visible in the Actions log. When it skips because a modified file's exact path is absent on a release branch, the author got no signal — a file moved or renamed after the branch was cut (e.g. coordinator/ on main vs controller/ on release/v1.2 in #6960) reads as "feature absent" and silently drops a backport the fix actually needed. Post a single, in-place-updated report comment (identified by a hidden marker, so `edited` re-runs update it instead of stacking): one row per actively-supported release branch stating whether the label was added (change detected), skipped (with the modified files that were absent and a prompt to add the label by hand), or declined (opt-out). The comment links the auto-label run. Authored by github-actions[bot] like the review request, so it needs no label PAT. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/30329940952 With regards, GitHub Actions via GitBox
