You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current contribution guidelines recommend using git add * to stage changes before committing. However, it's more conventional and safer to use git add . to stage changes in the current directory. The difference lies in the behavior of these commands, where git add * stages all changes in the current directory and its subdirectories, potentially including unintended files, while git add . stages changes only in the current directory without including untracked files.
Solution:
Update the contribution guidelines to recommend using git add . instead of git add * for staging changes before committing. This will ensure consistency and help contributors avoid accidentally staging files they didn't intend to include in their commits.
Screenshot:
In step 7 we can find this:
The text was updated successfully, but these errors were encountered:
Description:
The current contribution guidelines recommend using
git add *
to stage changes before committing. However, it's more conventional and safer to usegit add .
to stage changes in the current directory. The difference lies in the behavior of these commands, wheregit add *
stages all changes in the current directory and its subdirectories, potentially including unintended files, whilegit add .
stages changes only in the current directory without including untracked files.Solution:
Update the contribution guidelines to recommend using
git add .
instead ofgit add *
for staging changes before committing. This will ensure consistency and help contributors avoid accidentally staging files they didn't intend to include in their commits.Screenshot:
In step 7 we can find this:
The text was updated successfully, but these errors were encountered: