# Git commit email address

**URL:** <https://forum.codefloe.com/t/git-commit-email-address/69>\
**Category:** General\
**Created:** [November 24, 2025, 5:11pm UTC](https://forum.codefloe.com/t/git-commit-email-address/69 "2025-11-24T17:11:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![repzilon](https://forum.codefloe.com/user_avatar/forum.codefloe.com/repzilon/32/94_2.png) [@repzilon](https://forum.codefloe.com/u/repzilon)\
**Post date:** [November 24, 2025, 5:11pm UTC](https://forum.codefloe.com/t/git-commit-email-address/69/1 "2025-11-24T17:11:26Z")

</div>

Can I use a “noreply“ email address for my git commits instead of my account email address, like it is possible with Github?

---

<div class="post-metadata">

**Author:** ![repzilon](https://forum.codefloe.com/user_avatar/forum.codefloe.com/repzilon/32/94_2.png) [@repzilon](https://forum.codefloe.com/u/repzilon)\
**Post date:** [November 24, 2025, 9:02pm UTC](https://forum.codefloe.com/t/git-commit-email-address/69/2 "2025-11-24T21:02:15Z")

</div>

Oops, I haven’t read completely what is written below the “Hide email address“ preference. That preference could be made clearer in Foregejo by putting radio buttons instead of a checkbox like :

( ) Use my account address (…)  
( ) Use $account@noreply.$domain.$tld

---

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [November 25, 2025, 10:21am UTC](https://forum.codefloe.com/t/git-commit-email-address/69/3 "2025-11-25T10:21:11Z")

</div>

Great you found a solution! Note that we only use Forgejo as the underlying software, any questions around the core functionality and possible bugs and improvements should be made against the upstream repo directly: [forgejo/forgejo: Beyond coding. We forge. - Codeberg.org](https://codeberg.org/forgejo/forgejo)

While we have the option to apply changes or extend the functionality, we usually only do so for larger changes which are too debatable/large to get implemented into Forgejo directly. Such smaller changes would need to be improvement within Forgejo directly.