Merges, reverts and web edits made through the forge are stamped with the person's account email. On a public repository that address is published in every clone forever, and it cannot be taken back without rewriting history. A person's commit address should be one they chose to publish.
Acceptance criteria
[ ] Each account has a commit address setting. The default is a no-reply form on the forge's own host (for example <username>@users.noreply.<forge host>). Using the real email is an explicit opt-in on the account settings page.
[ ] Every commit the forge writes for a person (merge, squash, revert, web edit, new file, delete, conflict resolution) uses that address as author and committer.
[ ] The account email is never written into git objects, page metadata, the Atom feed or the API's public user view.
[ ] Tests: a merge and a web edit by a user with the default setting produce commits whose author and committer emails are the no-reply form. A user who opted in gets their email.
Merges, reverts and web edits made through the forge are stamped with the person's account email. On a public repository that address is published in every clone forever, and it cannot be taken back without rewriting history. A person's commit address should be one they chose to publish.
Acceptance criteria
<username>@users.noreply.<forge host>). Using the real email is an explicit opt-in on the account settings page.