3 ms·
I'm trying VSCode now, but I still switch back to Sublime for SublimeGit. It's such an integral part of my workflow, and VSCode's built-in git is no substitute
by bsimpson 9y ago
I'm trying VSCode now, but I still switch back to Sublime for SublimeGit. It's such an integral part of my workflow, and VSCode's built-in git is no substitute.
- komali2 9y agoI haven't tried sublimeGit - what's it got that I'm missing from VSCode's git? I only really use it to commit and compare when I'm merging.
- bsimpson 9y ago- You can easily see the status of each file (new, modified, or staged). - You can easily stage all files, each file, or just specific hunks of specific files. - You can stash and pop stashes. - You can amend a commit. - You can do all of that from the keyboard, without touching the mouse. I imagine you can do many of those things with VSCode, but it's so effortless in Sublime. I haven't learned the same workflow in VSC yet, and since I do all of those things frequently, I'm really attached to SublimeGit.
- penpapersw 9y agoIn the same way, I use VS Code mostly now (for node stuff) but I still load up Emacs and use Magit whenever I need to do serious version control, meaning basically anything more than just "glance at the changes and commit everything."