Show HN: Switch Git Users CLI

Post by jolmg » Thu, Nov 12, 2020, 8:36 PM UTC

varl wrote: post #45

jolmg wrote: post #44

Earlier quoted context omitted.

> git config --global alias.identity '! git config user.name "$(git config user.$1.name)"; git config user.email "$(git config user.$1.email)"; :' Why `; :` at the end?

I'm not entirely sure, but `:` means "true" in bash, and if I omit it, something like this happens: $ git config alias.foo '! echo "$1";' $ git foo bar bar echo "$1";: bar: command not found Whereas if I end with `; :` then it works as expected: $ git config alias.foo '! echo "$1"; :' $ git foo bar bar It seems to execute the last argument (`bar`) as a command without the `:` at the end, and I don't have a `bar` comm…

  argv_array_pushf(out, "%s \"$@\"", argv[0]);

Post by varl » Thu, Nov 12, 2020, 9:30 PM UTC

jolmg wrote: post #52

varl wrote: post #45

Earlier quoted context omitted.

I'm not entirely sure, but `:` means "true" in bash, and if I omit it, something like this happens: $ git config alias.foo '! echo "$1";' $ git foo bar bar echo "$1";: bar: command not found Whereas if I end with `; :` then it works as expected: $ git config alias.foo '! echo "$1"; :' $ git foo bar bar It seems to execute the last argument (`bar`) as a command without the `:` at the end, and I don't have a `bar` comm…

Seems it's to allow implicit and explicit use of arguments passed to alias. Git does the following to the alias string[1]: argv_array_pushf(out, "%s \"$@\"", argv[0]); So, you can have aliases like `!grep foobar` to automatically accept arguments or aliases like yours that use arguments explicitly. I've done aliases like `!bash -c 'foo $1' sh` before, but on seeing yours, I see that it was unnecessary to re-wrap with…

Post by jolmg » Thu, Nov 12, 2020, 10:42 PM UTC

lilyball wrote: post #55

jolmg wrote: post #52

Earlier quoted context omitted.

Seems it's to allow implicit and explicit use of arguments passed to alias. Git does the following to the alias string[1]: argv_array_pushf(out, "%s \"$@\"", argv[0]); So, you can have aliases like `!grep foobar` to automatically accept arguments or aliases like yours that use arguments explicitly. I've done aliases like `!bash -c 'foo $1' sh` before, but on seeing yours, I see that it was unnecessary to re-wrap with…

Huh I had no idea $1/$2/etc worked as-is in an alias. The advice I learned years ago for dealing with any alias that needs to do something custom with parameters is to write it like git config alias.foo '!f() { actual command goes here }; f' as that will pass all the args to the shell function. But if git is already setting it up so the args work then suffixing the alias with ";:" seems simpler.

Post by Ajedi32 » Thu, Nov 12, 2020, 11:48 PM UTC

gumby wrote: post #51

varl wrote: post #13

I found this user management strategy somewhere, and it's been working great for me: git config --global --unset user.name git config --global --unset user.email git config --global --unset user.signingkey git config --global user.useConfigOnly true git config --global user. .name " " git config --global user. .email " " git config --global alias.identity '! git config user.name "$(git config user.$1.name)"; git conf…

Good idea as it makes the trees "self describing". But: does this edit a file that can appear in .gitignore or are you uploading this to affect all your collaborators?

Post by gurjeet » Sat, Nov 14, 2020, 6:59 AM UTC

  [user]
    name = Gurjeet Singh
    # Tell Git to _not_ guess my name and email based on `whoami` and `hostname`
    useConfigOnly = true

  *** Please tell me who you are.*

  git config user.email me@example.com