Hacker News Reader

Comment by ggregoire | Hacker News Reader

VSCode handles this very well too: select the lines you want to commit and do "Git: Stage selected ranges"

I'd be careful with that feature though because it used to have an absolutely awful bug (and it might still tbh, I haven't had it confirmed that it's fully fixed yet).

https://github.com/microsoft/vscode/issues/96104

If you staged selected ranges it could change the line endings of the whole file from CRLF to LF. It's very easy to miss since it doesn't show in the normal diff, but then you end up with merge conflicts galore later on.

Yikes that sounds like something that could shred an entire codebase

That should only be a problem in windows.

VSCode's interface to Git is superior to Git-native. Adding the concept of Sync, simplifying branching, so many niceties.

i'm going to have to try vscode again, is this Sync you mention something other than the usual sync'ing of the user profile? what does vscode do differently with branches?

A Sync is a push+pull, changing branches is graphical.

you can add the concept of sync yourself in git.

    [alias]
      sync = "git squash && git pull --rebase && git pop && git push" # YMMV

Git GUIs are always changing the interface to git. It gives you this weird lockin and islandification. Knowing how to actually use git can give you super powers.

Reply on news.ycombinator.com