Skip to content

[Bug]: Not using git add . #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
CBID2 opened this issue Oct 21, 2024 · 1 comment · May be fixed by #5
Open

[Bug]: Not using git add . #4

CBID2 opened this issue Oct 21, 2024 · 1 comment · May be fixed by #5

Comments

@CBID2
Copy link

CBID2 commented Oct 21, 2024

Description

The Git flow workfile lists git add . as the command to stage commits. While true, the command developers are encouraged to use is git add file-nameso that the files they are not working on won’t be added to the staged commit(s).

Solution

Replace the command with the alternative mentioned above
@CBID2 CBID2 linked a pull request Oct 21, 2024 that will close this issue
Open
@pradeepsgouds
Copy link

It's very helpful that you pointed out the inclusion of git add . in the workflow documentation.

As you have rightly mentioned, using git add file-name is more accurate, particularly in collaborative projects, as staging unrelated changes can introduce bugs or confusion in subsequent commits.

This consideration requires developers to be more deliberate and thoughtful, which is important for clean versioning and collaboration with others.

Thank you for proposing the fix. I appreciate it and it looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: change add command CBID2/github-101
2 participants
@CBID2 @pradeepsgouds