Show HN: Git-Add–Interactive with Enhancements(github.com) I created a replacement for the perl git-add--interactive that adds a few enhancements: - S to automatically split all hunks - G to set a global filter on hunks to show - A to automatically accept all hunks (after auto-splitting and global filter are applied) |
Then I discovered Vim fugitive. It allows to go through the diff and stage chunks so intuitively, it changed the way I work. Just j/k to move around, = to expand file, s to stage selection, c to commit. The process of reviewing changes became very natural and actually enjoyable. I like the feeling of control it gives and how it makes focused commits painless while not disrupting the flow.
I knew that you could place a `git-xyz` executable and you can call it as `git xyz`. I didn't know you could do it with flags !?!
A small video or some screenshots would help a lot. If you can record interactivity with ascii-cinema, that will be even better.
i = !git add -N . && git add -p
** Commands **
1: status 2: update 3: revert 4: add untracked
5: patch 6: diff 7: quit 8: help
This allows you to either type in (p) or (5) to go into patch mode.
I think it’ll fit nicely alongside scmpuff which I’ve been using for years (and at this point refuse to ever give it up): https://github.com/mroth/scmpuff
As for licensing, I'm happy to change the license. I have no strong feelings on the subject, and don't know what restrictions GPLv2 imposes on a port to another language.
It often did the wrong thing IME, but YMMV.
Or at least, it would require first a massive effort to align the maintainers on the idea of a new language, like Rust in the Linux kernel
Just re-write in C
I made an alias a while ago I use frequently:
af => !f() { git add -p $(git diff --name-only | fzf); }; f
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.
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.
lazygit (of course): https://github.com/jesseduffield/lazygit
git-machete: https://github.com/VirtusLab/git-machete
rebase-editor: https://github.com/sjurba/rebase-editor
And that's probably not enough: for example likely you'd need to reuse whatever Git uses to generates patch formats. It's not necessarily _hard_, but it's not "just" a language translation.