Should I put my e-mail address in code?

One problem with placing your e-mail address in code is that, if it ever changes, you'll be left with a ton of files containing outdated contact information.

If somebody wants to contact you about your code, it might make sense for them to get your contact details from where that code came from.

My code is published on GitHub and my own website. These are the only two primary sources, and they both already contain my contact information. There are other places that the code winds up, like code archives and userscript websites like Greasyfork. In those cases, I try to always link to one of the primary sources to create a traversible path to my contact information. I keep the door just open enough.

It's easier for me to maintain only two sources than it is to worry about a mass of files. There's much less to maintain and therefore less room for error. Of course, I can automatically mass edit the contents of files, but is it really worth doing if I have to then synchronise every additional online copy of that file - be it on GitHub or wherever - individually? I don't think so. I'd rather just eliminate the trouble entirely.

Zooming out, it might be fair to call this kind of thinking an obsessive kind of future-proofing, but when we're talking about anything code-related, is that such a bad trait?

So, should I put my e-mail address in code?

I've realised I shouldn't - and maybe you shouldn't either. Spare yourself.