[Feature request] Allow conditionally setting the "Block command line pushes that expose my email" only for some e-mail addresses

[abjugard]

Select Topic Area

Product Feedback

Body

The "Block command line pushes that expose my email" feature is great, and helps immensely in allowing me to keep my private email private. But when I make commits to repos on my current employers GitHub organisation I need to commit using my work email. It is easy to handle setting the correct work email for those repos via ~/.gitconfig:

[includeIf "hasconfig:remote.*.url:[email protected]:WorkTenant/**"]
  path = .gitconfig-work
[includeIf "gitdir:~/code/work/"]
  path = .gitconfig-work

~/.gitconfig-work:

[user]
name = My Name
email = [email protected]

But then when I push in that repo I get:

~/code/work/some-work-project main* ⇡ 25s
❯ git push
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 12 threads
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 936 bytes | 936.00 KiB/s, done.
Total 9 (delta 6), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (6/6), completed with 2 local objects.
remote: error: GH007: Your push would publish a private email address.
remote: You can make your email public or disable this protection by visiting:
remote: https://github.com/settings/emails
To github.com:WorkTenant/some-work-project.git
 ! [remote rejected] main -> main (push declined due to email privacy restrictions)
error: failed to push some refs to 'github.com:WorkTenant/some-work-project.git'

I would like a way to individually disable that rule for specific email addresses (or GitHub organisations).

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Hanashiko]

Hi @abjugard ,

Thanks for raising this — it's a very valid use case and something that resonates with many developers working across both personal and professional GitHub environments.

The “Block command line pushes that expose my email” feature is indeed a great safeguard, especially when using a private GitHub email to keep your personal information secure. However, as you've pointed out, this becomes a bit restrictive when working in a professional context where your work email is intentionally used and necessary for compliance, auditing, or internal tooling.

While your current setup using conditional includes in ~/.gitconfig is a solid approach to separating identities, unfortunately GitHub currently applies the email protection rule universally. This means that even correctly configured work emails will trigger the protection mechanism if they are not explicitly made public in your GitHub email settings.

It would be ideal if GitHub allowed more granular control, such as the ability to:

• Whitelist specific email addresses,
• Disable the block for specific domains (e.g., @company.com),
• Or apply rules based on organization-level scopes.

For now, the only workaround is to add your work email to your GitHub account and mark it as "public" if you want to use it in commits without hitting this restriction — though I fully understand why that may not be ideal or even acceptable depending on your employer’s privacy policies.