Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I used Git on the command line exclusively for many years and occasionally tried the built-in Git tools for various editors as well as GitHub Desktop, but I never felt they were a lift in usability over the CLI or very pleasant to use. That was until I tried Sublime Merge on a whim. One thing I like is how keyboard oriented most of it is, and how it maps quite closely to CLI commands. If I want to commit I open the command palette with command+p and then fuzzy-search for commit with “co…” or “cm” or whatever you like, and it brings up the suggested commands which I can select with enter. And beyond that I like the generally attractive styling which makes viewing diffs and searching commit history (command+f, fuzzy find “contents:”, type what you want to search for) pleasant. It’s also totally snappy in most cases, even with multiple tabs for repos open — the only time I’ve seen it slow down was opening Unreal Engine, and that was at least a year ago so they may have made improvements on that. I use it every day and I am quite pleased with it.


> If I want to commit I open the command palette with command+p and then fuzzy-search for commit with “co…” or “cm” or whatever you like, and it brings up the suggested commands which I can select with enter.

cm is exactly how I think of commit, but I use it as a custom command on the cli.

I use my cm command like:

cm “Small refactoring of quux and baz”

and it runs

git commit -m “Small refactoring of quux and baz”

Similarly I have other two letter commands for all of the other git operations I most frequently use. (I.e for almost all of the ones I use day to day.)


Have you tried any TUI tools? I'm super happy with tig for visualizing history, diffs, staging chunks and staged/unchanged changes. For anything else I just use the git CLI commands.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: