Claude needs its own commit identity so PRs can be reviewed properly #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every commit on this repository is authored as
Justine Akehurst <justine@noreply.clowderlabs.com>, including the ones Claude wrote. My involvement appears only as aCo-Authored-Bytrailer in the message body.Why this blocks review
Code review depends on knowing who wrote what. Right now:
git blameandgit logattribute my work to you. A line I got wrong reads as a line you wrote, which is exactly backwards for the reviewer.--authorfiltering cannot separate the two. You cannot ask "what did Claude touch in the last week" or diff review standards between human-written and generated code.The
Co-Authored-Bytrailer does not fix this. It is unindexed free text in the message body, invisible to blame, log filtering, and the review UI.What would fix it
A separate Forgejo account, and commits authored as that account with you as committer where appropriate:
That is git's native distinction: author is who wrote the change, committer is who applied it. It preserves your control over what lands while making the authorship honest.
Open questions for you
--authoroverride alone fixes blame and log but leaves the PR still opened by you.Claude Opus 5names the model, which changes over time;Claude Codenames the tool, which is more stable.Notes
Account creation needs instance admin rights. The
teatoken here has repo scope only, sotea admin users listfails withtoken does not have at least one of required scope(s): [read:admin]. This one needs your hands.Decided: Claude Code as the identity, with a real Forgejo account.
Claude Codenames the tool rather than the model, so the attribution stays stable as the model behind it changes.What needs your hands
Account creation needs instance admin rights, which the
teatoken here does not have.Then grant it write access to
justine/fnameso it can push branches.What I can do without the account
Set
--authoron every commit I write, which fixesgit blame,git log --author, and the audit trail immediately. Forgejo will still show you as the PR author until the account exists and pushes under its own credentials, but the authorship inside the history becomes correct straight away.I will start doing that now and record it in the house rules.