4 ms·
That’s interesting - I haven’t seen GitHub’s privacy wrapper in their docs, do you have a link? I’ve gotten some spam, but so far it’s only come in to aliases
by fossuser 6y ago
That’s interesting - I haven’t seen GitHub’s privacy wrapper in their docs, do you have a link?
I’ve gotten some spam, but so far it’s only come in to aliases I haven’t made (like info@) which I think I can block in the fastmail settings.
- developer2 6y agoI did this a while ago for myself; it looks like the setting can be found here[1], labelled as a checkbox "Keep my email addresses private". Note that (I think, not sure if it gets overridden if you check the box), you also need to set your "user.email" git config to use the noreply email they provide. Personally, I'd never committed to an external 3rd-party repository, and I crushed/re-imported (erasing history) my own repositories using the new noreply email. This is because I know no external users were depending on my old repositories. I suspect that if you've already pushed commits to a 3rd-party repo, it's too late (the email address is part of the commit and cannot be revoked without a history-changing rebase). In my case, I deleted my repos and re-imported, history be damned. [1] https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address https://help.github.com/en/github/setting-up-and-managing-yo...
- fossuser 6y agoAh thanks - yeah I've already pushed with my new aliased email for git (I recently switched to Fastmail and set up a less extreme alias configuration :) ).