7 ms·
Another way to get that instead of behavior is with SSH configuration. I have something like this in my ssh config: Host github Hostname github.com
by NewJazz 3y ago
Another way to get that instead of behavior is with SSH configuration. I have something like this in my ssh config:
Host github
Hostname github.com
User git
Then you can do a "git clone github:microsoft/windows" and you're good to go.
- OJFord 3y agoTrue. If I'm only using it for git though makes sense to keep the config there IMO. But certainly that's handy when you're sshing interactively or doing other things with that host.
- jerpint 3y agoNeat
- hinkley 3y agoThis fuckin' guy. If you've evolved an SSO solution from brownfield, or just merged with another company you can easily end up in a spot where you have 2 user names across the systems, and that's before you get into doing things like pushing bug fixes to Github straight from your work machine. Make yourself an .ssh/config file. Set your user, and your ssh key for where it matters (I don't use the same key for ssh to servers and for talking to github or bitbucket)
- NewJazz 3y agoAy usually "this fucking guy" has a pejorative tone... I think you were agreeing with me but yeah not sure everyone understood the same.
- hinkley 3y agoThe show where everything is made up, and the points don’t count.
- saghm 3y ago> Make yourself an .ssh/config file. Set your user, and your ssh key for where it matters (I don't use the same key for ssh to servers and for talking to github or bitbucket) Another good setting for your ssh config if you use different keys for different servers is to require passing a key for all hosts rather than it trying each of your keys to see which one works: Host * IdentitiesOnly yes