Yicong-Huang opened a new pull request, #4676:
URL: https://github.com/apache/texera/pull/4676
## What changes were proposed in this PR?
In \`.github/workflows/direct-backport-push.yml\`, the \`push-backports\`
job's \`actions/checkout@v5\` step now passes \`token: \${{
secrets.AUTO_MERGE_TOKEN || secrets.GITHUB_TOKEN }}\`. The cherry-pick is then
pushed to the release branch under the PAT, which retriggers workflows
configured to run on push to release branches. Without this, the default
\`GITHUB_TOKEN\`-authored push is silently excluded from triggering downstream
workflows, so post-merge CI on backport commits never runs.
Falls back to \`GITHUB_TOKEN\` when the secret is unset, preserving current
behavior on forks without the secret.
## Any related issues, documentation, discussions?
Closes #4673. Follow-up to #4580 (post-merge backport automation) and #4594
(CI for release branches). Uses the same \`AUTO_MERGE_TOKEN\` PAT introduced
for the AutoQueue stand-in (#4553 / #4672).
## How was this PR tested?
Not yet — exercises only when a PR with a backport label is merged into
\`main\`. After landing and configuring the \`AUTO_MERGE_TOKEN\` repo secret,
plan to:
- [ ] Merge any PR carrying a backport label.
- [ ] Confirm a successful \`Direct Backport Push\` run.
- [ ] Confirm the resulting push on the release branch triggers the expected
post-merge CI run.
If \`AUTO_MERGE_TOKEN\` is not configured, the workflow falls back to
\`GITHUB_TOKEN\` and behavior is unchanged.
## Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7 (Claude Code)
--
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]
