正在加载视频...
视频加载失败
I betcha didn’t know about git add in patch mode!
35,642 次观看 • 2 年前 •via X (Twitter)
9 条评论

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.

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

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

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

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.

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

I did know about it, and once I found out about it I have never gone back.

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.

Stage this hunk baby



