Menu
A lot of times, I like to modify some lines of code in order to make debugging easier, but I don't actually want to commit them. For instance, I'll disable some annoying features (like ads) by commenting out some lines of code, or I'll set the log levels and filters to only the ones I care about, or I'll force a conditional to be true just so the block of code I want to run actually runs all the time.
In Perforce, I would have created a "changelist" for these files and labeled it as "DON'T COMMIT!". What would be the equivalent of this in Git? A branch doesn't work because these debug-only modifications need to exist with other changes I'm currently making.
951
The “changes not staged for commit” message shows when you run the “git status” command and have a file that has been changed but has not yet been added to the staging area. This is not an error message, rather a notification that you have changed files that are not in the staging area or a commit.
The "Staging Area" In Git, just because a file was modified doesn't mean it will be automatically included in the next commit. Instead, you have to tell Git explicitly which of your modifications shall be part of the next commit. This is done by adding a change to the Staging Area or, put simply, by "staging" it.
Lookup the --assume-unchanged option. There is a blog article about this which explains things quite well. And also this one which mentions finding such ignored files later on.
53
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
