Yicong-Huang opened a new pull request, #4614: URL: https://github.com/apache/texera/pull/4614
### What changes were proposed in this PR? The `Direct Backport Push` workflow added in #4598 commits the cherry-pick onto the release branch with \`github-actions[bot]\` as both author and committer. \`git config\` sets the bot identity before \`git commit -F -\` runs, and \`git cherry-pick --no-commit\` does not preserve the original commit's authorship in the index, so the bot identity sticks. This PR captures the squash-merge commit's author with \`git log -1 --format='%an <%ae>' \"\$MERGE_SHA\"\` and passes it via \`--author=\` to \`git commit\`. The resulting backport commit keeps the original PR author and only the committer stays as \`github-actions[bot]\`, which preserves the audit trail for the automated push. ### Any related issues, documentation, discussions? Follow-up to #4598. No new issue. ### How was this PR tested? Local verification of the commit-message construction: \`\`\`bash git cherry-pick --no-commit <merge_sha> git commit -F message --author='Original Author <[email protected]>' git log -1 --format='Author: %an <%ae>%nCommitter: %cn <%ce>' # Author: Original Author <[email protected]> # Committer: github-actions[bot] <github-actions[bot]@users.noreply.github.com> \`\`\` The next \`Direct Backport Push\` invocation against a release/* labelled PR will surface the new author on the cherry-picked commit on the release branch; existing backport commits already on release branches are unaffected. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.7 -- 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]
