+ [2016-03-19T20:50:38Z] VxJasonxV linuxmodder: yubikey only applies to 2FA insertion, and (GitHub's) SSH doesn't use 2FA.
+ [2016-03-19T20:52:29Z] Seveas s/[\(\)]//g # ssh in general can definitely use 2fa :)
+ [2016-03-19T20:53:11Z] Seveas this message is sent via a 2fa'd ssh connection :)
+ [2016-03-19T20:58:16Z] VxJasonxV (GitHub's) being the caveat
+ [2016-03-19T20:58:24Z] VxJasonxV contextual caveat

message no. 127525

Posted by tasmani_evil in #github at 2016-03-19T11:48:45Z

it does not work. Github says: "Where should we fork this repository? A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project."
+ [2016-03-20T00:23:06Z] Vainglory so is it my understanding that following https://help.github.com/articles/keeping-your-email-address-private/ your e-mail will not show up in commits or gits that you've done from the browser?
+ [2016-03-20T00:31:22Z] VxJasonxV Vainglory: yes, but only on new commits.
+ [2016-03-20T00:31:26Z] VxJasonxV see https://help.github.com/articles/keeping-your-email-address-private/#my-old-commits-still-have-my-old-email-address for fixing old ones
+ [2016-03-20T00:36:44Z] Vainglory well, i ask because i just made a new ( and only ) account. i'm coming over from bitbucket because they lack setting your e-mail private, you can still access 'public' repositories on a 'private' account, and you can't save a snippet without your e-mail being saved with it.
+ [2016-03-20T01:13:05Z] VxJasonxV it doesn't really matter about the account, it matters more about the information in the git repository