# gitcli(7) Manual Page

## NAME

gitcli - Git command-line interface and conventions

## SYNOPSIS

gitcli

## DESCRIPTION

This manual describes the convention used throughout Git CLI.

Many commands take revisions (most often "commits", but sometimes "tree-ish", depending on the context and command) and paths as their arguments. Here are the rules:

- Options come first and then args. A subcommand may take dashed options (which may take their own arguments, e.g. "--max-parents 2") and arguments. You SHOULD give dashed options first and then arguments. Some commands may accept dashed options after you have already given non-option arguments (which may make the command ambiguous), but you should not rely on it (because eventually we may find a way to fix these ambiguities by enforcing the "options then args" rule).

- Revisions come first and then paths. E.g. in , and are revisions and and are paths.

- When an argument can be misunderstood as either a revision or a path, they can be disambiguated by placing between them. E.g. 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 the difference between the HEAD commit and the work tree as a whole". You can say to ask for the latter.

- Without disambiguating , Git makes a reasonable guess, but errors out and asks you to disambiguate when ambiguous. E.g. if you have a file called HEAD in your work tree, is ambiguous, and you have to say either or to disambiguate.

- Because disambiguates revisions and paths in some commands, it cannot be used for those commands to separate options and revisions. You can use for this (it also works for commands that do not distinguish between revisions in paths, in which case it is simply an alias for ).

  When writing a script that is expected to handle random user-input, it is a good practice to make it explicit which arguments are which by placing disambiguating at appropriate places.

- Many commands allow wildcards in paths, but you need to protect them from getting globbed by the shell. These two mean different things:

      $ git restore *.c
      $ git restore \*.c

  The former lets your shell expand the fileglob, and you are asking the dot-C files in your working tree to be overwritten with the version in the index. The latter passes the 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 , you will not see in your working tree with the former, but with the latter you will.

- Just as the filesystem . (period) refers to the current directory, using a . as a repository name in Git (a dot-repository) is a relative path and means your current repository.

Here are the rules regarding the "flags" that you should follow when you are scripting Git:

- Splitting short options to separate words (prefer to , the latter may not even work).

- When a command-line option takes an argument, use the stuck form. In other words, write instead of for short options, and instead of for long options. An option that takes optional option-argument must be written in the stuck form.

- Despite the above suggestion, when Arg is a path relative to the home directory of a user, e.g. or , you may want to use the separate form, e.g. , not . The shell will expand in the former to your home directory, but most shells keep the tilde in the latter. Some of our commands know how to tilde-expand the option value even when given in the stuck form, but not all of them do.

- 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 but write ; the former will not work if you happen to have a file called in the work tree.

- Many commands allow a long option to be abbreviated only to their unique prefix (e.g. if there is no other option whose name begins with , you may be able to spell to invoke the 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. , to make a short prefix that used to be unique no longer unique.

## ENHANCED OPTION PARSER

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.

Here is a list of the facilities provided by this option parser.

### Magic Options

Commands which have the enhanced option parser activated all understand a couple of magic command-line options:

-h

  gives a pretty printed usage of the command.

      $ git describe -h
      usage: git describe [<options>] <commit-ish>*
         or: git describe [<options>] --dirty

          --contains            find the tag that comes after the commit
          --debug               debug search strategy on stderr
          --all                 use any ref
          --tags                use any tag, even unannotated
          --long                always use long format
          --abbrev[=<n>]        use <n> digits to display SHA-1s

  Note that some subcommand (e.g. ) may behave differently when there are things on the command line other than , but without anything else on the command line is meant to consistently give the usage.

--help-all

  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.

### Negating options

Options with long option names can be negated by prefixing . For example, has the option which is on by default. You can use to override that behaviour. The same goes for and .

### Options trump configuration and environment

When there is a configuration variable or an environment variable that tweak the behaviour of an aspect of a Git command, and also a command line option that tweaks the same, the command line option overrides what the configuration and/or environment variable say.

For example, the configuration variable is used to specify the human-readable name used by the command to record the author and the committer name in a newly created commit. The environment variable, if set, takes precedence when deciding what author name to record. The command line option of the command, when given, takes precedence over these two sources of information.

### Aggregating short options

Commands that support the enhanced option parser allow you to aggregate short options. This means that you can for example use or .

### Abbreviating long options

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, behaves as if you typed , but that is true only until a later version of Git introduces another option that shares the same prefix, e.g. option.

### Separating argument from the option

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:

    $ git foo --long-opt=Arg
    $ git foo --long-opt Arg
    $ git foo -oArg
    $ git foo -o Arg

However, this is NOT allowed for switches with an optional value, where the stuck form must be used:

    $ git describe --abbrev HEAD     # correct
    $ git describe --abbrev=10 HEAD  # correct
    $ git describe --abbrev 10 HEAD  # NOT WHAT YOU MEANT

## NOTES ON FREQUENTLY CONFUSED OPTIONS

Many commands that can work on files in the working tree and/or in the index can take and/or options. Sometimes people incorrectly think that, because the index was originally called cache, these two are synonyms. They are not— these two options mean very different things.

- The option is used to ask a command that usually works on files in the working tree to only work with the index. For example, , 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 option, it looks for strings in the index.

- The option is used to ask a command that usually works on files in the working tree to also affect the index. For example, usually merges changes recorded in a stash entry to the working tree, but with the option, it also merges changes to the index as well.

command can be used with and (but not at the same time). Usually the command only affects the files in the working tree, but with , it patches both the files and their index entries, and with , it modifies only the index entries.

See also https://lore.kernel.org/git/7v64clg5u9.fsf@assigned-by-dhcp.cox.net/ and https://lore.kernel.org/git/7vy7ej9g38.fsf@gitster.siamese.dyndns.org/ for further information.

Some other commands that also work on files in the working tree and/or in the index can take and/or .

- is exactly like , which is used to ask a command to only work on the index, not the working tree.

- is the opposite, to ask a command to work on the working tree only, not the index.

- The two options can be specified together to ask a command to work on both the index and the working tree.

## GIT

Part of the git(1) suite