The only sane way to do this is with a proper IDE. Doing it via the command line is pure masochism.
commit.verbose true This adds the whole commit diff in the text editor where you’re writing your commit message, to help you remember what you were doing.
https://jvns.ca/blog/2024/02/16/popular-git-config-options/#...
Regardless I also really like `git add -p`. I don't use it often but it really makes me focus on and consider each hunk. It was the defacto way to do it at an old company I worked at and no, it was not a small startup "hipster" company, we built enterprise ERP software.
(2/5) Stage this hunk [y,n,q,a,d,K,j,J,g,/,e,?]?
Wow, so intuitive! LOL. You really showed him.
This UX is laughably bad. It presents you every hunk, one at a time, without context, and if you want to include some lines and not others, you can't unless all the sub-hunks are exactly one line or you let it launch a text editor and you dick around in the raw diff which is its own domain-specific language.
Why don't people play starcraft like this?
(1/1) Move this zergling [u,d,l,r,b,a,J,g,/,e?]?
The fact that this needs a write-up and discussion is all you need to know. Where is the big how-to for committing partial files in GitHub Desktop? Oh, yeah, nobody needs one because it's obvious and right in front of your face.
If you have no limbs and can't use a mouse to click on things then this UI is great though.
The ‘s’ to split changes is one of my favorite feature.
It takes a few minutes to get used to it, then becomes automatic: add the whole file ‘a’, skip file ‘d’, skip chunk ‘n’, stage chunk ‘y’, split ‘s’, stop here ‘q’, rollback ctrl-c.
The “chunk per chunk” approach is actually really nice, you’re focusing on what exactly you want to get your commit to be about.
You learn it once, that will never change, you’re set for decades.
EDIT:
You have extremely low standards for what constitutes a professional tool these days.
You also didn't address my point. split is brain damaged and doesn't work:
+ assertEquals(byte[].class, p.get0().getClass());
+ assertEquals(String.class, p.get1().getClass());
-p makes you more productive because you don't know how to use an electron app or Java app
It's like you're saying "guys you should use this new hand drill I've discovered! It's so much more productive than digging holes with an awl!" while ignoring the fact that electric drills exist.
Oh, I forgot that it probably couldn't be fixed even if they wanted to because if split suddenly started working it would break someone's spacebar heating script.
If you personally prefer a GUI then that’s obviously your choice. Some people do and I doubt you’ll find many people claiming Git has the world’s best UI. It does work everywhere, though, and I doubt it’s any slower than using a GUI for a task like your example. Either way, you can have lines staged or not pretty much as fast as you can read them and decide whether they should be.