56 ms·
Git Add -p
- cratermoon 5y agoThe author enables auto-formatting and linting in his editor. He then runs into the problem of huge and meaningless diffs when working on code that doesn't conform to the formatting and linting settings. His solution is to add complexity, effort (and opportunity for errors) to the process, rather than thinking, "maybe automatically reformatting the source code is something that should be done more selectively".
- joshbetz 5y agoMost of the code I work on actually does conform to the formatting and linting settings. Once in a while I'll work on something that doesn't and if I've already written some code, I find it's easier to stage part of the changes like this. Obviously do what works for you.
- WhyNotHugo 5y ago`git add -p` is super useful. (1) you get to review changes as you stage them, which is good to confirm that all the changes still make sense. (2) if you have _some_ changes that you want to commit, but not others, this avoids screwing up. Honestly, I can't image using git without this. Oh, and, please, don't use `git add .` and blindly stage+commit changes. It's honestly one of the worse common practices I've seen around.