I betcha didn’t know about git add in patch mode!
@wesbos448K followers
35,650 views
9 Comments
Comments from the original post on X (Twitter)

@acemarke
This is by far the biggest reason I've always preferred using a Git GUI for commits in most cases - the ability to visually pick and choose which hunks (or individual lines) get added, rather than using a TUI. Fork's great. Used to use SourceTree. VS Code's UI is awkward.
34 likes

@liran_tal
patch mode is great but how cool that you can do exactly that in VS Code's UI? :-)
6 likes

@gnarf
I almost always use -p. I actually have an alias that tracks new files without adding the lines so -p can catch them I use this step as a sort of self code review and reminder to remove console statements etc before it gets pushed
2 likes

@maznevskia
git add -p is quite useful to interactively review and stage changes chunk by chunk. Note: This only stages modifications to existing files, not new files, meaning that they won't be added
1 like

@localpcguy
So glad to see this featured! I've been telling coworkers and anyone who will listen about using patch for years. Even have it aliased to `git ap`. Next do `git add -i` (or `--interactive`) for more command line fun, can do patch, but also revert, add files and more.
1 like

@AndyHails
"that was my band name in high school" actually made me do a spit take with my coffee! 😂
1 like

@mayorbyrne
I did know about it, and once I found out about it I have never gone back.
1 like

@SergiiShymko
IntelliJ IDEs allow you to pick and choose which changes to include in a commit. Uncheck the checkbox of unwanted changes from the diff viewer. Using this all the time along with moving some changes out to a separate Change Set.

@JoeAttardi
Stage this hunk baby
