Specify an email address to use for commits to an organization's repositories

[garretmh]

When creating a commit through the GitHub website (e.g. when merging a PR) a user's primary email address is always used. But when working on an organization's code it may be preferable to use an organization-specific email address.

It is already possible to specify an organization-specific email address for notifications and it would be very helpful for GitHub to use that same email address when committing to organization-owned repositories.

[Levi-Lesches]

To add some context, this causes major issues in some cases:

• When the PR is being merged via a squash commit, the email addresses of the committer(s) is lost
• When the PR author doesn't have write-access, the repo manager merges, and their email is recorded
• The above case

[zomars]

Also there's more discussion in this issue: todogroup/gh-issues#32

[sudoforge]

IMO, this is a gaping flaw and needs to be a high priority issue for the team to resolve.

[CowChris]

Yes please!

[SethAngell]

Wanted to bump this. Setting a default email address for all web gui actions on a per-organization basis would be highly desirable

[oshaughnessy]

Adding another request & data point here. This would be so valuable, and changing the default would probably match expected behavior much more than the current design.

I'll repeat what I just posted in todogroup's GH Issue 32:

It has always seemed logical to me that when I join an org, if I have an email address associated with my GitHub account in that org's verified domains, all my PR approvals and merges should start to use that email address. As things stand now, I'm part of an org with 50+ repos, and as part of the devops team, I'm a reviewer or new committer to new repos all the time. I have to maintain constant vigilance when I'm reviewing and merging to be sure I've chosen the right address. I think GitHub could offer a much more sensible default in this scenario.

[christianbundy]

The de facto workaround for this is to have all everyone create a new GitHub account specifically for each organization, which is inconvenient and undermines GitHub's goal of individuals having one account. I'd love to be able to advocate for individuals only having one GitHub account, but until this is resolved I'm inclined to recommend that every company makes employees create a GitHub account specifically for work.

[phlickey]

i don't want people at work to be able to git blame my personal email address after i retire please github

[weibelben]

You should be able to configure an org based custom route under notifications settings

https://github.com/settings/notifications/custom_routing

[garretmh]

This discussion is about using an org email for commits created within GitHub not notifications.

The original post explicitly mentions that this is not about notifications.

[mscottford]

That said, perhaps the custom routing that's used for notifications could be expanded to also affect the email that's used for authoring commits that are made via GitHub.

[ArcanisCz]

Hi @weibelben custom routing only affects notifications (and for that case it works).

[zzJinux]

Closely related: https://github.com/orgs/community/discussions/10840

[nnutter]

I noticed today that if I merge I can choose my identity but not if using the merge queue feature.