4 ms·

You need to sign a CLA to work on Go, like most Google projects. You can't accidentally use your personal email address, and setting up the CLA signing stuff is

• dmoy 7y ago
  But you can (and are encouraged to?) sign up using your personal email while still employed at Google.
  • joshuamorton 7y ago
    The opposite is true. You are explicitly asked to make all contributions while at Google (to all projects) under your @google email.
    • dmoy 7y ago
      Ok that's curious, cus I've spent the last two years working on a project at Google that's half open source, and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. But this is also like a developed-in-open-source project, not a built-internally-and-copied-outside, so maybe the guidance differs there? Or is that a go team specific thing?
      • joshuamorton 7y ago
        > and the guidance we got was to use an existing non-google github account for contributions if you had one and wanted to. This is correct. Use an existing github account, but your contributions should be under your @google email address. There's nothing that ties your github account to a git email. I've committed through github from like 4 different email addresses (@google, @gmail, @uni.edu, and a shared organizational one for a project from a shared machine).
        • dmoy 7y ago
          Ah gotcha, yes we're agreed then. The underlying commits are supposed to be tied to your @google account (though a not insignificant number slip through)