Make the cross-forge bot the primary native commit author #576
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#576
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?
Native Codex and Claude commits currently keep Kai as the primary Git author and place the cross-forge bot plus active harness in Co-authored-by trailers. Forgejo only renders the primary author visibly, while GitHub renders recognized coauthors. Swap the native attribution order for future agent-issued commits: use the SSM-derived GitHub App noreply identity as the primary author, preserve Kai as a Co-authored-by trailer using the repository-resolved Git identity, and retain the active Codex or Claude trailer. Human commits and non-commit Git calls must remain unchanged. Keep the local identity config secret-safe, fail closed on incomplete attribution, extend focused tests, update docs, reconcile locally, and verify the resulting commit resolves to the bot on both forges.