Honest question: what's up with the <i>(2 hours ago)</i> notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads to me trying to calculate the actual date from it because that just works for me, being used to it. Same with e.g. Thunar: to me it's maddening that it defaults to displaying 'today/sunday/saturday' <i>and</i> then mixes that with plain dates for timestamps older than a week (or so). Can be me, but this is just so confusing and harder to parse?
I really liked the look of this, until I got to `save`/`sync` in the readme...<p>That's not how I want to work, and it's not how I want other people to work in a repository I'm using. I <i>know</i> 'I don't have to use them then I can just use the git subcommands', but that's not the point, it's a big signal ('90% of the time the above commands will have you covered.') about the motivation/angle/philosophy of the project that doesn't match my attitude towards git at all.<p>Which is a shame, because the autocomplete stuff looks really nice.
Git is an awesome tool – so awesome that it has a vast plethora of options and commands to do just about anything. Bit attempts to alleviate some of that pain.
> <a href="https://news.ycombinator.com/item?id=24173238" rel="nofollow">https://news.ycombinator.com/item?id=24173238</a><p>Super cool and thanks for this! I commented a few weeks ago on how it'd be nice to have a git CLI that actually helps you find the command you're looking for because you don't really know what to search for unless you know what command to use with git. It's sort of this chicken-and-egg problem that this seems to help solve.
The autocomplete popups are really cool.<p>Does anyone know if there's a generic way to provide this for all tools with CLI's with help text? What about being able to parse a Programmable Completion file.<p>I don't know much about this stuff, but the thought popped into my mind.
It’s not mentioned in the README, but is WSL2 on the Windows Terminal app supported?<p>I could run gnome terminal but then I have to configure X11 and that’s a pain.<p>Thanks, this looks awesome.
The autocomplete/help popups didn't happen for me, is there something I need to do? I'm using zsh on a Mac, perhaps it assumes bash.<p>Aside from that, I'm going to persist with this for a little while and see how it goes, the git interface does bother me.
There is another alternative called gitgud if you want more of a gui interface.
<a href="https://github.com/GitGud-org/GitGud" rel="nofollow">https://github.com/GitGud-org/GitGud</a>
Cool project! Love the autocomplete feature. Just my 2 cents about the custom commands, hiding the complexity of git commands is not something I'd like personally (not accounting for alias, aliases are cool). In most cases you'd much rather know which exact git command did/does what to debug/fix, so it's better to invest that time learning early on..