Task Summary
The backport auto-label workflow decides per release branch whether to add a release/* label, but skips are only visible in the Actions log. When it skips because a modified file's exact path is absent on a release branch, the author gets no signal — e.g. #6960 (fix(amber): reply to portCompleted…) was not labeled for release/v1.2 because its files live under coordinator/ on main but controller/ on the release branch, so the fix silently missed a backport it needed.
Make the workflow post a single, in-place-updated report comment: one row per actively-supported release branch stating whether the label was added (change detected) or skipped and why, linking the auto-label run, so the author can review and add a missed label by hand.
Task Type
Task Summary
The backport auto-label workflow decides per release branch whether to add a
release/*label, but skips are only visible in the Actions log. When it skips because a modified file's exact path is absent on a release branch, the author gets no signal — e.g. #6960 (fix(amber): reply to portCompleted…) was not labeled forrelease/v1.2because its files live undercoordinator/on main butcontroller/on the release branch, so the fix silently missed a backport it needed.Make the workflow post a single, in-place-updated report comment: one row per actively-supported release branch stating whether the label was added (change detected) or skipped and why, linking the auto-label run, so the author can review and add a missed label by hand.
Task Type