I have also seen some really long/complex-looking git aliases that are really hard to follow, like:
[alias]
foo = !"f() { some; really && long | function onliner || with lots of $(sed) && awk '{print $1}' && then call --it at 'the' end ; } ; f"
For these cases, I would recommend creating an executable script placed somewhere in your $PATH named git-foo and git will expose this as a subcommand, like $ git foo. Just like git-extras.
I have also seen some really long/complex-looking git aliases that are really hard to follow, like:
For these cases, I would recommend creating an executable script placed somewhere in your
$PATHnamedgit-fooand git will expose this as a subcommand, like$ git foo. Just like git-extras.Agreed, as an alias abuse that's just obnoxious.