4 ms·
This post is a great reference of what’s possible with git config wrt includes/remotes, and I’m sure I’ll be getting back to it. One thing though: what’s the p
by ku1ik 2y ago
This post is a great reference of what’s possible with git config wrt includes/remotes, and I’m sure I’ll be getting back to it.
One thing though: what’s the point of using separate keys for work/personal/github/gitlab? I fail to see a practical and security advantage over using one key (per workstation).
- gloflo 2y agoPrivacy for sure. It's no ones business to know how certain accounts are related.
- ku1ik 2y agoAh, right. E.g. using separate GH accounts for personal and work. Forgot about that!
- carbonboarder 2y agoGitHub does not allow you to share a key with another GitHub account anymore
- computerfriend 2y agoThey never did. The account is identified by the key, so it's impossible.
- ku1ik 2y agoOf course! I’ve been using separate GH accounts for work and personal stuff in the past myself. It’s been years since then and I completely forgot. In fact, I was one of not too many who used separate account for work, and people didn’t understand it, wondering why the hassle.
- ku1ik 2y agoTo add to my other replies to replies in this thread… These days I prefer to use local VMs to compartmentalize different areas of work (personal, consulting, etc) so my git config is plain and simple. Lately I’ve been doing mostly consulting work around open-source so I’ve been using my primary GH account for the most part, but separate VMs allow me to use a different key (account) without advanced git config incantations.