[GH] (texera/ci/8377-open-a-pr-for-clean-backports): Workflow run "Backport Checks" is working again!

[GitBox <gi...@apache.org>]

The GitHub Actions job "Backport Checks" on texera.git/ci/8377-open-a-pr-for-clean-backports has succeeded.
Run started by GitHub user mengw15 (triggered by mengw15).

Head commit for run:
ad317e4435c26aa206d668e6726828be07b2043b / mengw15 <12...@users.noreply.github.com>
ci: open a pull request for a clean backport instead of pushing it

Direct Backport Push cherry-picks a cleanly-applying fix onto the release
branch and pushes it. Every one of those pushes has been rejected since
2026-07-24 -- release/* is covered by the Merge Queue ruleset, which
requires a pull request for everyone -- and ASF policy asks for prior
Infrastructure authorization before an automated service writes a branch
subject to official release. #8379 tried to exempt the Actions app from
the ruleset; GitHub refuses to create that bypass, so the fast path has
never once worked since it broke.

Both outcomes now open a pull request. The conflicted one is unchanged:
a draft, assigned to its author. A clean one opens ready for review,
assigned to nobody, because there is no code for anyone to write on it.

What a clean backport still needs is its checks started. GitHub creates
no workflow run for anything GITHUB_TOKEN does, so a bot-opened pull
request has none, and nothing will arrive on its own: with no run there
is no re-run, and none of the three required workflows listens for
ready_for_review. Reopening the pull request, or pushing to its branch,
is what emits an event they subscribe to -- so the PR says exactly that,
in the comment the conflict path already uses for its instructions.

That leaves the release manager with three ordinary buttons: reopen,
approve, and auto-merge if they would rather not come back for the
checks. Nothing here depends on a token's pull-request scope, on an
Actions bypass, or on a close/reopen the workflow performs itself -- the
paths that can only be proven in production, and that fail quietly when
they are wrong.

push_entries is now always empty, leaving push-backports unreachable.
Removing it is left to a separate change, so that this one is a
behaviour change and that one is a pure deletion.

Report URL: https://github.com/apache/texera/actions/runs/35573925360

With regards,
GitHub Actions via GitBox