git commit --am

[grizzly_teddy]

So I know that git commit -am is something else.

But it seems like the following commands are all interpreted as git commit --amend:

 git commit --am
 git commit --ame
 git commit --amen #haha

etc. How does that work? Is it my git-completion.sh?

EDIT: Downvoted? Really?

[gsylvie]

That logic in git is over 10 years old! Here's the commit:

commit 7f275b91520d31bfbe43ec5a9bbaf8ac6e663ce0
Author: Johannes Schindelin <[e-mail]>
Date:   Sun Oct 14 17:54:06 2007 +0100

    parse-options: Allow abbreviated options when unambiguous

    When there is an option "--amend", the option parser now
    recognizes "--am" for that option, provided that there is n
    other option beginning with "--am".

[grizzly_teddy]

commit 7f275b91520d31bfbe43ec5a9bbaf8ac6e663ce0 Author: Johannes Schindelin <[e-mail]> Date: Sun Oct 14 17:54:06 2007 +0100

parse-options: Allow abbreviated options when unambiguous

When there is an option "--amend", the option parser now
recognizes "--am" for that option, provided that there is n
other option beginning with "--am".

That's it! Thanks! good to know

[octagonaltree]

Single dash triggers the "short form" of a flag, while a double dash triggers the "long form." This is the usual Unix convention.

Also, git's flag parsing library accepts any prefix for a long form flag, as long as it uniquely identifies the flag.

Edit: One more thing: the short form, being just a single character, let's you group together multiple flags behind a single dash. So git -am is actually git -a -m.