What's the difference between:
git add .
git commit -a
Should I be doing both, or is that redundant?
What's the difference between:
git add .
git commit -a
Should I be doing both, or is that redundant?
git commit -a
means almost[*] the same thing as git add -u && git commit
.
It's not the same as git add .
as this would add untracked files that aren't being ignored, git add -u
only stages changes (including deletions) to already tracked files.
[*] There's a subtle difference if you're not at the root directory of your repository. git add -u
stages updates to files in the current directory and below, it's equivalent to git add -u .
whereas git commit -a
stages and commits changes to all tracked files.
git add -u
will become like git commit -a
; you will need to explicitly say git add -u .
if that is what you mean. –
Throckmorton git add .
behaves in a different way. –
Bushweller git commit -a
automatically invokes git add
on all files it knows about. You can use git add
to select what files to commit. Consult the docs for more info: here
git add -u
–
Lousy By using the git commit -a switch with the commit command to automatically "add" changes from all known files (i.e. all files that are already listed in the index)
© 2022 - 2024 — McMap. All rights reserved.