A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels. Archive: https://archive.sweetops.com/random/
GitHub CLI 1.0 is here Take GitHub to the command line and interact with repositories, issues, pull requests, releases, and more. ✓ Free and open … 155 comments on LinkedIn
If I’m part of an organization…. rather than setting the email address of the commit to my work email, what is the negative of just using my standard
[users.noreply.com](http://users\.noreply\.com) github email associated to my user. Since the commits are all private in the org, I’m wondering why I bother setting it to my work email in the commit history in the first place. Any reason to do this?
Note, I just figured out mailmap, which I found interested. It got me to thinking that it’s all mixed up mostly with folks anyway, so why not just use the exact same one regardless of org or not?
@users.noreply.github.com at work and there are no issues
got you. i’ve set a separate one per profile in each repo, but now just thinking why do I bother
||stories](https://krebsonsecurity.com/2020/09/the-joys-of-owning-an-og-email-account/) of why you shouldn’t use emails like that. He just wrote about this yesterday actually. But someone owns
When you own a short email address at a popular email provider, you are bound to get gobs of spam, and more than a few alerts about random people trying to seize control over the account. If your account name is short and desirable enough, this kind of activity can make the account less reliable…
Sorry that’s not what we are talking about
This is a subdomain for github, to protect email privacy being mapped directly in the commit history
Gotcha. Yeah I saw the
[users.noreply.github.com> and saw that was okay; I saw the bare
<http://users.noreply.com|users.noreply.com](http://users\.noreply\.github\.com) and was worried for you