4 ms·
In the beginning I tried to use git exclusively through command line because I thought that's how real men do it. But after using gitkraken (or similar product
by yoodenvranx 9y ago
In the beginning I tried to use git exclusively through command line because I thought that's how real men do it.
But after using gitkraken (or similar products) I will never go back to using git through its command line interface. Being able to see the whole repo structure is just so much more convenient and it helps to resolve most merging problems much faster. git guis all have their own problems, but overall using a git gui for me is the better choice in 95% of all use cases.
- michaelgrafl 9y agoI always have both open. Gitkraken for having a broad overview of local and remote branches, stashes, and for staging chunks of code. And the command line for everything else. Some things just confuse me in any GUI Frontend or don't work as fast as on the CLI.
- cbcoutinho 9y agoThis is what I do too. I like looking at my entire staging area commits using the CLI, but merging makes much more sense using GitKraken. Version control is just too complicated of a problem (for me) to reason about in one 'view', and using different tools to look at separate scales of a repository is the way I've found to work through that difficulty.
- bauerd 9y agoFirst time I hear of gitkraken but why would a Git repository viewer have me create an account!?
- jononor 9y agoYeah being able to see what you do is critical for understanding and feeling comfortable. I do everything via "git", but always have "gitk" open for that visual overview. gitk is very basic and not that great, but does the trick.