GUM: A better CLI for Git
saintsjd.com
GUM: A better CLI for Git
1–10 of 85 posts
Re: GUM: A better CLI for Git
#2https://github.com/saintsjd/gum
but the idea sounds great!
Re: GUM: A better CLI for Git
#3I feel like when the interface is a side-effect of implementation, you get a more gradual sliding scale from user to developer (like being able to experiment with web apis by curling at them).
In git's case, I appreciate that I can trawl around through my .git directory and not get lost because it pretty closely matches the interface.
Re: GUM: A better CLI for Git
#4Re: GUM: A better CLI for Git
#5Also I'm really tired of messing with ~/.gitmodules and unwieldy *submodule-commands that demand to be executed in the project-root all the time. Why can't we simply "git add" sub-repositories, perhaps bailing with a warning by default and an extra-flag to really do it...
Re: GUM: A better CLI for Git
#6That said, take the time and learn what git does and how it works and it makes a ton of sense. It's remarkably simple, and then the commands map directly to what you're doing to your history, which is utterly fantastic.
Re: GUM: A better CLI for Git
#7No doubt Git gods who have every nuance of the system memorized can take advantage of the flexibility of the (IMHO) complicated and obtuse CLI. But for schmucks like me who just want to get work done and not worry about it, something like this would be a godsend.
I've more than once thought about switching away from Git just because I'm scared I'll do the wrong command and mess something up--and I've been programming for 15 years.
Re: GUM: A better CLI for Git
#8Re: GUM: A better CLI for Git
#9Re: GUM: A better CLI for Git
#10Is it possible for all of these to be implemented as git command aliases?