Skip to content

upstreaming: author and commit fork patches as the App - #4981

Open
luhenry wants to merge 2 commits into
mainfrom
upstreaming-pipeline
Open

luhenry wants to merge 2 commits into
mainfrom
upstreaming-pipeline

Conversation

@luhenry

@luhenry luhenry commented Nov 20, 2026

Copy link
Copy Markdown
Member

Summary

  • Configure the worker checkout identity as the riseproject-dev App bot.
  • Make the trusted publisher authoritative: after applying a proposal in a fresh repository, recreate every commit in the linear series with the App bot as both author and committer.
  • Preserve each commit's tree, message, parent order and author/committer timestamps while replacing identity.
  • Use GitHub's bot noreply identity:
    riseproject-dev[bot] <330740410+riseproject-dev[bot]@users.noreply.github.com>.

Why both layers

Agent-created mboxes can otherwise retain github-actions[bot] or model-side Git configuration as author while the trusted publisher supplies a different committer. Final fork history must not trust agent-selected identity. The fresh reconstruction now normalizes both fields immediately before validation and push.

Validation

  • 183 tests pass.
  • Local bare-repository publication coverage verifies the pushed commit has the App bot as author and committer.
  • Tree, operation receipt, path/history validation and exact-head lease behavior remain unchanged.
  • All gh-aw v1.2.2 generated locks match.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant