To be fair, you can always set something similar up on your own that isn’t tied to any specific forge; you can set your git email to something like sinkhole at domain dot tld, where the domain is one you control.
Then have your mail server put anyone who sends email to the sinkhole address onto a spamlist, as they’re harvesting git logs for emails. Only turn it off temporarily when adding the sinkhole as a commit address to a git forge.
A bit more complicated, but you can genericize the setup.
I also looked it up, and Forgejo apparently also allows you to do this, but it’s controlled by an admin setting and the address you’re meant to use is in a popover (and is only documented in their configuration file). It uses the structure username at noreply dot DOMAIN, with DOMAIN being the domain forgejo is running on. That means pretty much every git hosting tool of note that isn’t just “here’s the repo and a clone url” supports it. (Since selfhosting is pretty much either Gitlab or Forgejo these days.)
To be fair, you can always set something similar up on your own that isn’t tied to any specific forge; you can set your git email to something like sinkhole at domain dot tld, where the domain is one you control.
Then have your mail server put anyone who sends email to the sinkhole address onto a spamlist, as they’re harvesting git logs for emails. Only turn it off temporarily when adding the sinkhole as a commit address to a git forge.
A bit more complicated, but you can genericize the setup.
I also looked it up, and Forgejo apparently also allows you to do this, but it’s controlled by an admin setting and the address you’re meant to use is in a popover (and is only documented in their configuration file). It uses the structure username at noreply dot DOMAIN, with DOMAIN being the domain forgejo is running on. That means pretty much every git hosting tool of note that isn’t just “here’s the repo and a clone url” supports it. (Since selfhosting is pretty much either Gitlab or Forgejo these days.)
score 1 · canonical