4 ms·

Why do you need to use different name/key/email between work and personal project?

Terr_ 7y ago
Well, the e-mail part is pretty straightforward, since many people will have a personal e-mail and a separate e-mail managed by their workplace IT. If some current (or future) coworker has a question about the code, I don't want them to necessarily e-mail me on my home account. I might not be checking it during work hours, or I might not even be with the company anymore. Similarly, if someone actually wants to contact my e-mail for a hobby-project, I don't want them to send it to my work-account, which over time I might no longer have access to anyway.
- lloeki 7y ago
  This also applies to e.g CI systems, that are able to send build success/fails emails to the emails in the commits instead of the default GitHub/GitLab email.
  - WhyNotHugo 7y ago
    Actually, both GitLab and GitHub allow configuring different email addresses per team. The notifications don't go to the email in the git commit.
- moooo99 7y ago
  > Similarly, if someone actually wants to contact my e-mail for a hobby-project Also, some people prefer to not disclose their employer on GitHub hobby projects (or at all on the web). Simiarly, your employer doesn't necessarily need to know about every hobby project you start (as long as you're not violating work-contract clauses).
DrKabab 7y ago
In many workplaces, you're required to use the company provided email address with git. And the name some people use at work isn't the same as what they use in their personal projects. (For ex, I use my full name at work but a shorter one for personal stuff)
sirn 7y ago
Can be a lot of reasons. Some people (like me) like to keep their personal identity and work identity separated. Also some company policies forces you to use a different SSH key/GPG key for work-related stuff.
maeln 7y ago
I have to do this too because I work for different client and every client have their own gitlab which they only give access to account with their corporate email. So i have to commit under myname@client1.com for client 1, my.name@client2.fr for client 2 and so on. Since I usually have to work on several repositories, I usually do what OP presented. I have one directory per client with each their own configuration and their repositories.
- pampa 7y ago
  I used to have the client per directory setup too. But then took it one step further. Now for every client i set up a separate VMWare Workstation virtual machine with all the relevant git config files, ssh keys, software and build dependencies etc. That way every client is compartmentalized and there is limited chance of data or code leaking between clients. And i can always mid-session put the VM on pause, switch to another client and then resume right where i left, with all the editor windows open and services running. I call it the container approach to workspaces.
  - chrisweekly 7y ago
    Sounds good. +1 for writing it up and sharing dets! :)
  - p_l 7y ago
    Sounds a bit like what Qubes does

Well, the e-mail part is pretty straightforward, since many people will have a personal e-mail and a separate e-mail managed by their workplace IT. If some current (or future) coworker has a question about the code, I don't want them to necessarily e-mail me on my home account. I might not be checking it during work hours, or I might not even be with the company anymore. Similarly, if someone actually wants to contact my e-mail for a hobby-project, I don't want them to send it to my work-account, which over time I might no longer have access to anyway.

lloeki 7y ago
This also applies to e.g CI systems, that are able to send build success/fails emails to the emails in the commits instead of the default GitHub/GitLab email.
- WhyNotHugo 7y ago
  Actually, both GitLab and GitHub allow configuring different email addresses per team. The notifications don't go to the email in the git commit.
moooo99 7y ago
> Similarly, if someone actually wants to contact my e-mail for a hobby-project Also, some people prefer to not disclose their employer on GitHub hobby projects (or at all on the web). Simiarly, your employer doesn't necessarily need to know about every hobby project you start (as long as you're not violating work-contract clauses).

DrKabab 7y ago

In many workplaces, you're required to use the company provided email address with git. And the name some people use at work isn't the same as what they use in their personal projects. (For ex, I use my full name at work but a shorter one for personal stuff)

sirn 7y ago

Can be a lot of reasons. Some people (like me) like to keep their personal identity and work identity separated. Also some company policies forces you to use a different SSH key/GPG key for work-related stuff.

maeln 7y ago

I have to do this too because I work for different client and every client have their own gitlab which they only give access to account with their corporate email. So i have to commit under myname@client1.com for client 1, my.name@client2.fr for client 2 and so on. Since I usually have to work on several repositories, I usually do what OP presented. I have one directory per client with each their own configuration and their repositories.

pampa 7y ago
I used to have the client per directory setup too. But then took it one step further. Now for every client i set up a separate VMWare Workstation virtual machine with all the relevant git config files, ssh keys, software and build dependencies etc. That way every client is compartmentalized and there is limited chance of data or code leaking between clients. And i can always mid-session put the VM on pause, switch to another client and then resume right where i left, with all the editor windows open and services running. I call it the container approach to workspaces.
- chrisweekly 7y ago
  Sounds good. +1 for writing it up and sharing dets! :)
- p_l 7y ago
  Sounds a bit like what Qubes does