NAME<\/a> gitcli \u2212 Git command\u2212line interface and conventions<\/p>\n gitcli<\/p>\n This manual describes the convention used throughout Git CLI.<\/p>\n Many commands take revisions (most often “commits”, but sometimes “tree\u2212ish”, depending on the context and command) and paths as their arguments. Here are the rules:<\/p>\n \u2022 Revisions come first and then paths. E.g. in git diff v1.0 v2.0 arch\/x86 include\/asm\u2212x86<\/b>, v1.0<\/b> and v2.0<\/b> are revisions and arch\/x86<\/b> and include\/asm\u2212x86<\/b> are paths.<\/p>\n \u2022 When an argument can be misunderstood as either a revision or a path, they can be disambiguated by placing \u2212\u2212<\/b> between them. E.g. git diff \u2212\u2212 HEAD<\/b> is, “I have a file called HEAD in my work tree. Please show changes between the version I staged in the index and what I have in the work tree for that file”, not “show difference between the HEAD commit and the work tree as a whole”. You can say git diff HEAD \u2212\u2212<\/b> to ask for the latter.<\/p>\n \u2022 Without disambiguating \u2212\u2212<\/b>, Git makes a reasonable guess, but errors out and asking you to disambiguate when ambiguous. E.g. if you have a file called HEAD in your work tree, git diff HEAD<\/b> is ambiguous, and you have to say either git diff HEAD \u2212\u2212<\/b> or git diff \u2212\u2212 HEAD<\/b> to disambiguate.<\/p>\n \u2022 Because \u2212\u2212<\/b> disambiguates revisions and paths in some commands, it cannot be used for those commands to separate options and revisions. You can use \u2212\u2212end\u2212of\u2212options<\/b> for this (it also works for commands that do not distinguish between revisions in paths, in which case it is simply an alias for \u2212\u2212<\/b>).<\/p>\n When writing a script that is expected to handle random user\u2212input, it is a good practice to make it explicit which arguments are which by placing disambiguating \u2212\u2212<\/b> at appropriate places.<\/p>\n \u2022 Many commands allow wildcards in paths, but you need to protect them from getting globbed by the shell. These two mean different things:<\/p>\n $ git restore *.c The former lets your shell expand the fileglob, and you are asking the dot\u2212C files in your working tree to be overwritten with the version in the index. The latter passes the *.c<\/b> to Git, and you are asking the paths in the index that match the pattern to be checked out to your working tree. After running git add hello.c; rm hello.c<\/b>, you will not<\/i> see hello.c<\/b> in your working tree with the former, but with the latter you will.<\/p>\n \u2022 Just as the filesystem .<\/i> (period) refers to the current directory, using a .<\/i> as a repository name in Git (a dot\u2212repository) is a relative path and means your current repository.<\/p>\n Here are the rules regarding the “flags” that you should follow when you are scripting Git:<\/p>\n \u2022 it\u2019s preferred to use the non\u2212dashed form of Git commands, which means that you should prefer git foo<\/b> to git\u2212foo<\/b>.<\/p>\n \u2022 splitting short options to separate words (prefer git foo \u2212a \u2212b<\/b> to git foo \u2212ab<\/b>, the latter may not even work).<\/p>\n \u2022 when a command\u2212line option takes an argument, use the stuck<\/i> form. In other words, write git foo \u2212oArg<\/b> instead of git foo \u2212o Arg<\/b> for short options, and git foo \u2212\u2212long\u2212opt=Arg<\/b> instead of git foo \u2212\u2212long\u2212opt Arg<\/b> for long options. An option that takes optional option\u2212argument must be written in the stuck<\/i> form.<\/p>\n \u2022 when you give a revision parameter to a command, make sure the parameter is not ambiguous with a name of a file in the work tree. E.g. do not write git log \u22121 HEAD<\/b> but write git log \u22121 HEAD \u2212\u2212<\/b>; the former will not work if you happen to have a file called HEAD<\/b> in the work tree.<\/p>\n \u2022 many commands allow a long option \u2212\u2212option<\/b> to be abbreviated only to their unique prefix (e.g. if there is no other option whose name begins with opt<\/b>, you may be able to spell \u2212\u2212opt<\/b> to invoke the \u2212\u2212option<\/b> flag), but you should fully spell them out when writing your scripts; later versions of Git may introduce a new option whose name shares the same prefix, e.g. \u2212\u2212optimize<\/b>, to make a short prefix that used to be unique no longer unique.<\/p>\n From the Git 1.5.4 series and further, many Git commands (not all of them at the time of the writing though) come with an enhanced option parser.<\/p>\n Here is a list of the facilities provided by this option parser.<\/p>\n Magic Options<\/b> \u2212h<\/p>\n gives a pretty printed usage of the command.<\/p>\n $ git describe \u2212h \u2212\u2212contains find the tag that comes after the commit Note that some subcommand (e.g. git grep<\/b>) may behave differently when there are things on the command line other than \u2212h<\/b>, but git subcmd \u2212h<\/b> without anything else on the command line is meant to consistently give the usage.<\/p>\n \u2212\u2212help\u2212all<\/p>\n Some Git commands take options that are only used for plumbing or that are deprecated, and such options are hidden from the default usage. This option gives the full list of options.<\/p>\n Negating options<\/b> Aggregating short options<\/b> Abbreviating long options<\/b> Separating argument from the option<\/b> $ git foo \u2212\u2212long\u2212opt=Arg However, this is NOT<\/b> allowed for switches with an optional value, where the stuck<\/i> form must be used:<\/p>\n $ git describe \u2212\u2212abbrev HEAD # correct Many commands that can work on files in the working tree and\/or in the index can take \u2212\u2212cached<\/b> and\/or \u2212\u2212index<\/b> options. Sometimes people incorrectly think that, because the index was originally called cache, these two are synonyms. They are not<\/b> \u2014 these two options mean very different things.<\/p>\n \u2022 The \u2212\u2212cached<\/b> option is used to ask a command that usually works on files in the working tree to only<\/b> work with the index. For example, git grep<\/b>, when used without a commit to specify from which commit to look for strings in, usually works on files in the working tree, but with the \u2212\u2212cached<\/b> option, it looks for strings in the index.<\/p>\n \u2022 The \u2212\u2212index<\/b> option is used to ask a command that usually works on files in the working tree to also<\/b> affect the index. For example, git stash apply<\/b> usually merges changes recorded in a stash entry to the working tree, but with the \u2212\u2212index<\/b> option, it also merges changes to the index as well.<\/p>\n git apply<\/b> command can be used with \u2212\u2212cached<\/b> and \u2212\u2212index<\/b> (but not at the same time). Usually the command only affects the files in the working tree, but with \u2212\u2212index<\/b>, it patches both the files and their index entries, and with \u2212\u2212cached<\/b>, it modifies only the index entries.<\/p>\n See also https:\/\/lore.kernel.org\/git\/7v64clg5u9.fsf@assigned\u2212by\u2212dhcp.cox.net\/<\/font><\/b> and<\/font> https:\/\/lore.kernel.org\/git\/7vy7ej9g38.fsf@gitster.siamese.dyndns.org\/<\/font><\/b> for further information.<\/font><\/p>\n Some other commands that also work on files in the working tree and\/or in the index can take \u2212\u2212staged<\/b> and\/or \u2212\u2212worktree<\/b>.<\/font><\/p>\n \u2022 \u2212\u2212staged<\/b> is exactly like \u2212\u2212cached<\/b>, which is used to ask a command to only work on the index, not the working tree.<\/font><\/p>\n \u2022 \u2212\u2212worktree<\/b> is the opposite, to ask a command to work on the working tree only, not the index.<\/font><\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
ENHANCED OPTION PARSER<\/a>
NOTES ON FREQUENTLY CONFUSED OPTIONS<\/a>
GIT<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
$ git restore *.c<\/p>\nENHANCED OPTION PARSER <\/a> <\/h2>\n
Commands which have the enhanced option parser activated all understand a couple of magic command\u2212line options:<\/p>\n
usage: git describe [
or: git describe [
\u2212\u2212debug debug search strategy on stderr
\u2212\u2212all use any ref
\u2212\u2212tags use any tag, even unannotated
\u2212\u2212long always use long format
\u2212\u2212abbrev[=
Options with long option names can be negated by prefixing \u2212\u2212no\u2212<\/b>. For example, git branch<\/b> has the option \u2212\u2212track<\/b> which is on<\/i> by default. You can use \u2212\u2212no\u2212track<\/b> to override that behaviour. The same goes for \u2212\u2212color<\/b> and \u2212\u2212no\u2212color<\/b>.<\/p>\n
Commands that support the enhanced option parser allow you to aggregate short options. This means that you can for example use git rm \u2212rf<\/b> or git clean \u2212fdx<\/b>.<\/p>\n
Commands that support the enhanced option parser accepts unique prefix of a long option as if it is fully spelled out, but use this with a caution. For example, git commit \u2212\u2212amen<\/b> behaves as if you typed git commit \u2212\u2212amend<\/b>, but that is true only until a later version of Git introduces another option that shares the same prefix, e.g. git commit \u2212\u2212amenity<\/b> option.<\/p>\n
You can write the mandatory option parameter to an option as a separate word on the command line. That means that all the following uses work:<\/p>\n
$ git foo \u2212\u2212long\u2212opt Arg
$ git foo \u2212oArg
$ git foo \u2212o Arg<\/p>\n
$ git describe \u2212\u2212abbrev=10 HEAD # correct
$ git describe \u2212\u2212abbrev 10 HEAD # NOT WHAT YOU MEANT<\/p>\nNOTES ON FREQUENTLY CONFUSED OPTIONS <\/a> <\/h2>\n