Great Tool JLord! But emails exposed through git log - not too cool without notice. Not sure newbies realize this...

[CaliGRITS]

NOTE I do not get notifications for new issues created in this repository (because there are so many PRs coming through as people do the challenges it would flood my inbox) so if you open an issue you must ping me, @jlord.

Also please consider if your issue is actually with Git-it or reporobot as this repository is generated by those two.

[raistael]

@CaliGRITS - this is actually more tied to your GitHub settings for email and your local git config (where the username was added) than anything else. There's an option to keep your email address private inside your account settings here, which will mask your email with a noreply alternative, but this is only for web-based operations. Anything pushing up to the remote will rely on your gitconfig user.email to sort of "sign" the commit. There is a global config which affects all repos created, and a local config for each repo. If all you use is GitHub, then the global config will suit your purposes for most things, and you can drop your freshly masked email alternative into this user.email property to let your commits be signed by it instead of your private email. If you use git across several hosts, it might be better to just modify it on the local config on a case-by-case basis, though.