3 ms·
I'm a serial "git add -p" user. (Micro-review before every commit is super healthy imo). I made an alias a while ago I use frequently: af => !f() {
by jasonjmcghee 1y ago
I'm a serial "git add -p" user. (Micro-review before every commit is super healthy imo).
I made an alias a while ago I use frequently:
af => !f() { git add -p $(git diff --name-only | fzf); }; f
When you have a large diff, it's get unruly quickly to "add -p".
This just prompts you with a fuzzy find of the files that have changed and you can just pick one to go through the "add -p" process for that file.
For the terminal averse, IDEs usually have "jump to next change" and a tab for the changed files that can achieve the same.
- Night_Thastus 1y agoI used to do patch operations and hunk-editing for everything and really enjoyed it. It definitely helps to put a fresh view on the code and see anything missed. Eventually I moved on to going line-by-line with a GUI tool. In my case Git-cola, but I'm not positive I'd recommend it because it's quite slow on Windows.
- h1fra 1y agosame I just wish it would split things even more by default
- deleted 1y ago[deleted]