3 ms·
I'd be interested to know what, according to you, are the worst part of git commands (I'm currently trying to figure out a better CLI on top of libgit2).
by littlestymaar 6y ago
I'd be interested to know what, according to you, are the worst part of git commands (I'm currently trying to figure out a better CLI on top of libgit2).
- ByronBates 6y agoLet me reply with the most tedious parts, as I wouldn't want to make the impression of labelling git as 'bad' - I have been fascinated by it for more than 10 years now and it's time to scratch my itch for good. Please note that everything I name can certainly be fixed by some tool that already exists, and that's great. It's just that I would like to have 'this one tool' that gets most things right and be happy with it alone. That said, here is my list: * adding individual files to the staging area/index * looking at the commit history and copying individual commit hashes * pulling while assuring no merge commit is created, or: simplified trunk-based development * resumable clones * seeing what's going on during all remote operations - here in China GitHub is incredibly slow most of the time and connections can be flaky
- littlestymaar 6y agoThanks! That's really interesting to see that only 2 of your list (around adding and pulling) were on my radar as git usability issue, and not even in my top five! The third one is a bit unclear to me: > looking at the commit history and copying individual commit hashes What do you mean exactly by that?
- ByronBates 6y agoI frequently use `tig` to see the commit history, and pull out a single commit hash for use in `git checkout` or to reference it elsewhere. Probably it's just me not knowing all the `tig` hotkeys to make that easy, but it's my hope to have `gitoxide` as an obvious way to do things at least I need commonly.