git git git git git - CaiusTheoryEver found you&rsquo;ve accidentally entered too many gits in your terminal and wondered if there&rsquo;s a solution to it? I quite often type git then go away and come back, then type a full git status after it. This leads to a lovely (annoying) error out the box:<br>$ git git status<br>git: 'git' is not a git command. See 'git --help'.

What a git.<br>My initial thought was overriding the git binary in my $PATH and having it strip any leading arguments that match git, so we end up running just the git status at the end of the arguments. An easier way is to just use git-config&rsquo;s alias.* functionality to expand the first argument being git to a shell command.<br>git config --global alias.git '!exec git'

Which adds the following git config to your .gitconfig file<br>[alias]<br>git = !exec git

And then you&rsquo;ll find you can git git to your heart&rsquo;s content<br>$ git sha<br>cc9c642663c0b63fba3964297c13ce9b61209313

$ git git sha<br>cc9c642663c0b63fba3964297c13ce9b61209313

$ git git git git git git git git git git git git git git git git git git git git git git git git git git sha<br>cc9c642663c0b63fba3964297c13ce9b61209313

(git sha is an alias for git rev-parse HEAD.)<br>See what other git alias&rsquo; I have in my ~/.gitconfig, and laugh at all the typo corrections I have in there. (Yes, git provides autocorrection if you enable it, but I&rsquo;m used to these typos working!)<br>Now git back to doing useful things!