Home / Questions / 269266
Accepted
ASASCED
Asked: 2020-06-04 12:14:31 +0800 CST 2020-06-04 12:14:31 +0800 CST

Differences in git commands

  • 772

I would like to know what is the difference between git addand git add --.

After having tried them I have definitely not found any differences, but I have seen that some people, on some occasions, use one command or another, however I do not know how they really differ.

git

3 Answers

  1. Best Answer

    The commands:

    git add .

    Like:

    git add -A

    And also like:

    git add --all

    They serve to indicate that any file is going to be attached to the stage, from that point these files and their changes will be monitored

    Of the last 2 you can check it by executing the following command in any project that is being monitored by git:

    git add --help

    Which will show you between more commands a line like this:

    -A, --all add changes from all tracked and untracked files

    Now the command

    git add —

    According to the git documentation it says

    This option can be used to separate command-line options from the list of files, (useful when filenames might be mistaken for command-line options).

    Which can be translated as:

    this option can be used to separate command line options from the list of files, useful when file names can be confused with command line options.

    References

    • 25

  2. Well according to the documentation found on the internet and the help of the commands themselves in the terminal,

    git add .

    is used to add the files from the current directory where you are to the stage zone, and if you write

     git add --all

    It will serve you the same as putting the point . At least as far as I know from my own experience and seeing answers to questions similar to yours. I think in the end the one that is most comfortable and fastest for you.

    If it helps, for more info look at this answer given in the stackoverflow in English https://stackoverflow.com/a/26039014/10515716

    • 8

  3. The difference would become obvious if you had a file that is called as an option that can be passed to git.

    $ touch -- --force # no solo funciona para git el truco de --
$ ls -l
-rw-r--r-- 1 myself myself 0 Oct 19 19:55 --force
$ git add --force
Nothing specified, nothing added.
hint: Maybe you wanted to say 'git add .'?
hint: Turn this message off by running
hint: "git config advice.addEmptyPathspec false"
$ git add -- --force
$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
        new file:   --force

    The logic is simple... and it applies to many other commands, not just git. The --is used to tell a command that it's out of options and what comes (usually) are file names. For example:

    $ echo -n hola
hola$ echo -- -n hola
-- -n hola
$
    • 2