Popular posts

You're very rigth.

I found this answer with a very useful table stackoverflow.com/a/26039014

git add . does add changes in subdirectories. Also, i generally discourage using such shorthands as itʼs easy to add dangerous files like credentials or local only env files to the repository this way. You should add files one by one. If you have to add a large set of files in one commit, something is wrong anyway ☺

Gergely Polonkai are you 100% sure about that? I just googled a bit, it seems that git add . does not affect subdirectories.

Quote from the article below:

There's a problem with the "git add ." command. Since we're currently working in the root directory, "git add ." will only add files located in the root directory. But the root directory may contain many other directories with files. How can we add files from those other directories plus the files in the root directory to the staging area? Git offers the command below: $ git add --all

I am 100% positive, take a look:

$ git version 
git version 2.21.0

$ git status
On branch master
Untracked files:
  (use "git add <file>..." to include in what will be committed)

    a/a2
    b

nothing added to commit but untracked files present (use "git add" to track)

$ git add .

$ git status
On branch master
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

    new file:   a/a2
    new file:   b

Milica Maksimović ^

And it works even if the file in the subdirectory is not new but modified:

$ git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   a/a2

no changes added to commit (use "git add" and/or "git commit -a")

$ git add .

$ git status
On branch master
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

    modified:   a/a2

Yup, you're right. I guess this was the case in the past. I'll edit the original comment! Thanks!