> are YOU tired of typing every git command directly into the terminal<p>I'm not. Are there many people that are? Is this not just a matter of learning to use shell keybindings effectively? That and aliases does wonders to avoid repetitive typing. Many times I type `git s` (alias for `git status -s`) out of reflex when I really meant to do `ls`.<p>When I forget to add `-a` to `git ci -m ...` (`ci` being `commit`) and get an error because the index is empty, I just `<caps>kF-aa<enter>` (<caps> being <esc>) to add it and re-execute. It's muscle memory; I do it before I even realize I did it.
Awesome work OP! I’m a big fan of using tools like this to supplement git, especially when it comes to some of the more complex operations.<p>Personally I use tig, which is basically this but different. I used to use Sourcetree and I loved it but it slowed to a crawl with bigger projects with long histories.<p><a href="https://github.com/jonas/tig" rel="nofollow">https://github.com/jonas/tig</a><p>Best screenshots I can find on google are ironically from the Atlassian blog:<p><a href="https://www.atlassian.com/blog/git/git-tig" rel="nofollow">https://www.atlassian.com/blog/git/git-tig</a>
If you're an emacs user, I can't recommend magit [1] enough. I was a diehard CLI user and had flags and aliases out the wazoo, and it was still a step change in usabilty and power for me. Staging hunks, rebasing, and stashing are all vastly easier. Amending or editing a commit is a breeze, and it's tied in to all of the other emacs tools you already use, e.g. org-mode to boot!<p>It's easier to see it in action than explain it. If you've two minutes to spare, check out this emacsrocks screencast [2], or Howard Abram's longer presentation from the PDX Emacs Hackers meetup [3].<p>[1]: <a href="https://magit.vc/" rel="nofollow">https://magit.vc/</a><p>[2]: <a href="https://www.youtube.com/watch?v=rzQEIRRJ2T0" rel="nofollow">https://www.youtube.com/watch?v=rzQEIRRJ2T0</a><p>[3]: <a href="https://www.youtube.com/watch?v=vQO7F2Q9DwA" rel="nofollow">https://www.youtube.com/watch?v=vQO7F2Q9DwA</a>
> are YOU tired of typing every git command directly into the terminal, but you're too stubborn to use Sourcetree because you'll never forgive Atlassian for making Jira? This is the app for you!<p>lol
You know what would make me faster at git?<p>"git undo" : undo the last git command line, whatever it did. Especially if you don't understand what it did or it overwrote local files.
Hey guys thanks for all the feedback so far! I whipped up a quick tutorial for anybody who wants to know the basics <a href="https://www.youtube.com/watch?v=VDXvbHZYeKY" rel="nofollow">https://www.youtube.com/watch?v=VDXvbHZYeKY</a>
This looks great. For some reason I don't mind using the GUI tools to view history and branches but for commits always use the command line. This should save some time and much typing.
I'm mostly using plain Git, but there's one thing for which I needed a TUI: line-by-line selective committing.<p>After trying to find something I liked, I ended up porting crecord extension for Mercurial to Git: <a href="https://github.com/andrewshadura/git-crecord" rel="nofollow">https://github.com/andrewshadura/git-crecord</a>
Personally I have been typing all git commands manually into the terminal and never felt a need for GUIs or tools such as this.<p>There are a number of git shortcuts defined in my zsh aliases [0]. It goes like:<p><pre><code> # Git aliases
alias g='git'
alias ga='git add'
alias ghb='git browse' # hub
alias ghpr='git pull-request' # hub
alias gp='git push'
alias gpoh='git push origin HEAD'
...
</code></pre>
Using these aliases, we rarely have to type more than 3-4 characters for a git command. Savings and efficiency not only add up over years of using git, but also accelerate as you become more proficient in using your own aliases that fit your special needs.<p>[0] - <a href="https://github.com/sungwoncho/dotfiles/blob/master/zsh/aliases.zsh" rel="nofollow">https://github.com/sungwoncho/dotfiles/blob/master/zsh/alias...</a>
But why? There are so many awesome tools like tig and magit!<p>- <a href="https://github.com/jonas/tig" rel="nofollow">https://github.com/jonas/tig</a><p>- <a href="https://magit.vc/" rel="nofollow">https://magit.vc/</a>
Thanks for making this, it looks great! I'll be giving it a shot tomorrow.<p>I've been moving more and more to terminal for all of my development. My dev. stack is now: vim; tmux; lynx; ddgr; zsh; and docker. It is game changing for distraction-free programming, consistency between languages, and the ability to use the exact same setup everywhere -- even on remote machines.
I've been using Fork: <a href="https://git-fork.com/" rel="nofollow">https://git-fork.com/</a> because of its 2 primary advantages over SourceTree:
• Dark mode
• Tabs
I have been using <a href="https://github.com/scmbreeze/scm_breeze" rel="nofollow">https://github.com/scmbreeze/scm_breeze</a>, and though not as feature-packed, it does make the workflow fast.
I’ve yet to find a git setup that is more productive (for me at least) than SublimeGit for Sublime Text. The combination of a text based interface with single character shortcuts, and the quick support for staging individual parts of files, means I’m probably twice as fast as the next best thing. It’s the reason I haven’t moved from Sublime to VS Code.<p>This looks like it could be close, and I’ll definitely give it a try. If I could decouple myself a bit more from Sublime that would be great. The plugin community just isn’t the same as VS Code.
One Git UI that I absolutely love but I rarely see mentioned is GitKraken. It's so nice having a fully cross-platform Git GUI, that's attractive and intuitive.
'Go' question that came up when I tried to build this: How do you build a Go .EXE on Windows that doesn't have any file paths embedded in it?
How much time do people spend messing with their source control that extreme tools like this become necessary?<p>I commit like, once a day. What am I doing wrong?
Nice idea - I don't like going too far above the git cli, but I usually find myself building a set of terminals watching different git commands such as status, log, diff etc for a more parallel overview...<p>This tool looks like it does that a bit better with interactivity maintained, and for some reason i'm more comfortable accepting a CLI git UI into my workflow than a GUI.
I've always been a fan of Git Town: <a href="https://github.com/Originate/git-town" rel="nofollow">https://github.com/Originate/git-town</a><p>Not a UI but helps with some commands you run in a row quite often
Might be a good opportunity to advertise my git-send bash function / zsh plug-in:<p><a href="http://github.com/robertzk/send.zsh" rel="nofollow">http://github.com/robertzk/send.zsh</a>
I used to race and coach skiing for many years. Intermediate skiers always used to ask me what skis to buy to make them better at [ice|powder|moguls|steeps|etc] while I and most proficient skiers used the same boards every day in all conditions. This tool reminds me of that.<p>* I acknowledge that some really great skiers are geeked on their equipment and use a variety of skis. Point still stands.
Why not just use an actual GUI then rather than a shitty TUI?<p>GitX (Mac only sadly) is the best of the free ones, and Tower is then best of the commercial ones. Try those.
>>but you're too stubborn to use Sourcetree because you'll never forgive Atlassian for making Jira? This is the app for you!<p>This is the most ridiculous ad ever.