Yicong-Huang opened a new issue, #6119:
URL: https://github.com/apache/texera/issues/6119
### What happened?
`direct-backport-push.yml` resolves exactly one PR per push event — from
`head_commit.message` (or `commits/{context.sha}/pulls` as fallback). When
several auto-merges land on `main` within one ref update, only the push's head
commit is examined, and the `release/*` labels on every other PR in the same
push are silently dropped: no workflow run, no commit status, no failure
comment.
Audit of 2026-06-01 → 2026-07-04: 43 merged PRs carried `release/v1.2`; 2
never reached the branch — #5802 (coalesced with #5809/#5811/#5812, head #5812
was the only one processed) and #6111 (coalesced with #6112). The discover step
should iterate every commit in the push (e.g. compare `payload.before...after`)
and fan the matrix out over (PR, target) pairs.
### How to reproduce?
Merge two PRs into `main` close enough together that their squash commits
arrive in one push event, with the earlier PR labeled `release/v1.2`. Only the
later PR is backported; the earlier one is skipped without notice (see #5802,
#6111).
### Version/Branch
1.3.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
b0996e43b (skipped #5802), 6829fae77 (skipped #6111)
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
```
--
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]
