6 ms·
I can't believe no one has responded yet with "use a GUI". After gaining a basic understanding of how branches and merges work, and I do mean basic, I've never
by eyelidlessness 10y ago
I can't believe no one has responded yet with "use a GUI". After gaining a basic understanding of how branches and merges work, and I do mean basic, I've never been able to screw up a local repo with a GUI client enough that I haven't been able to recover with the same GUI tools.
I understand that people need to know how to use their tools, but for git most people can get away with the very basic usage that GUIs provide. If you've made some unrecoverable mistake with an important set of changes, you can always review the history in the same GUI and reimplement the important changes in a new branch.
- pauljaworski 10y agoI like to use a GUI for things like viewing staged/unstaged files, their riffs, and picking which files to stage for a commit, but for every other situation, the command line is just so much faster and easier to understand what's actually happening.
- mmusc 10y agoAgreed, a GUI have most of the functionality and a clear visual representation of the state of your repo. When it's not enough the terminal is once click away
- K0nserv 10y agoI have to disagree, I've seen people paint themselves into really hard to get out of corners by using GUI tools and not understanding the underlying tool. git GUIs are leaky abstractions that sometimes even change the meaning of core git concepts. I always recommend people start by using git at the command line until the have a solid understanding of how the tool works before switching to a GUI.
- noufalibrahim 10y agoYes. I teach git professionally and when I do, my approach is to stick to describing the nuts and bolts. Once people use it from the command line and get things done, they (usually) understand what's going on pretty well but are annoyed by the nitty gritties of the command line. Then they're ready to move on to a tool of their choice but can always map the actions there back to the data structures inside git so they've never lost. Also, they can always drop back down to the command line for any low level surgery that the client doesn't provide. I use magit myself for most things.
- mewm 10y agoI completely agree with this one. I encourage our developers to always use the cli, even if they are not familiar with the core concepts of git. I see myself as a mediocre git user, but there are some situations, however, where I prefer to use a GUI for more complex operations, like staging/un-staging specific lines or create/apply patches.
- lordnacho 10y agoI agree. If you use something like SourceTree, you can also see the git command, in case you end up needing to know what it is. Best of both worlds. I mainly use the GUI for day-to-day stuff. Only in rare cases will I need to mess with the command line.
- Pica_soO 10y agoOh, i did, yes i did. I wish there was a refund on wasted life. Process Explorer- are those crashed git instances still around? Yes. Can i kill them now with admin priv? Nope. Gui still frozen? Yes. Can i get Git-bash? Yes. Can i do something usefull with it? No, session is still open in the gui. No, don't get all riled up. I know what you will tpye beneath this. "..Put all the dummys in a reeducation camp, with electric fences around it.." ".. cementing superiority is what is all about, fuck the specialization that got humanity this far.." didn't sound like a opinion that can change the last time.
- breatheoften 10y agoIts true -- and actually the well designed gui that accurately depicts the graphical state of your local repository makes it far easier to learn the concepts behind git than does the command line. Distributed vc is conceptually nuanced, but not overly complicated -- the complexity of git really is in the interface wherein you are asked to map command line syntax into abstract operations that manipulate a state that you actually can't easily see from the command line. The value of having a graphical depiction of the state that's changing as you invoke operations should not be underestimated. http://gitup.co http://gitup.co I love this tool -- it's honestly one of the best graphical tools I've ever used -- rock solid reliable -- intuitive, not leaky in the abstractions it represents -- and not limited to only "simple" operations. And with the graphical reflog history rollback view -- it's always really easy to back up however far you want if you mess up which gives great confidence as you explore the ui's features. Ive taken designers from "never used git" to confidently pushing, pulling, rebasing, and resolving conflicts in less than a day (and most of it after the first 10 minutes without outside help).
- sillysaurus3 10y agoJust ran `brew cask install gitup`, cd'd into my repo and ran `gitup`. Took about 60 seconds and so far it's quite impressive. Clicking on a commit and pressing space brings up a view showing a github-style diff, a list of all changed files, and the complete commit message. Nice. Thanks for the tip!
- breatheoften 10y agoHappy to share! I had to do a site visit with a customer recently and spent some time pair programming on their codebase -- on a Windows machine and they used an awful git client -- really reminded me how much I appreciate using gitup!
- lnalx 10y agoOnly for iUsers... Really searching for a Linux alternative !
- 10y ago
- edem 10y agoI stopped using a GUI (SmartGit) when I encountered an error which was talking about stashes and something like {0}. I had no idea what the error was. Now I know how these tools work but I think that you can only use them effectively if you learn how they work and how the underlying system works. If you fail to do so you end up with a leaky abstraction which will at some point (and believe me it will) present you with an error message you don't understand and you end up with a problem you can't recover (yet). GUIs are fine but only if you know the ins and outs of the underlying system.
- Stratoscope 10y agoI'm with you. I've been using SmartGit for years and would never go back to the weak sauce of the command line, except for a few odd things that SmartGit doesn't cover (like bisect). Every one of the tasks in the article is a simple, straightforward operation in SmartGit. Take "I accidentally committed something to master that should have been on a brand new branch!" or "I accidentally committed to the wrong branch!" for example. Instead of an obscure series of four to six commands, you simply go to SmartGit's log view and drag the branch markers to where you want them. Easy and intuitive. I know GUI tools are a hard sell for a lot of programmers. I honestly don't understand why. I think it may be the fear that you'd be giving up power, but SmartGit isn't a dumbed-down GUI. It gives you a more powerful set of tools, and much more visibility into the state of your repo. You're not even giving anything up. You can still use the command line whenever you want, and SmartGit shows you the commands it used to accomplish each task. Of course you still need to understand the underlying Git concepts to use any GUI effectively, but a tool like SmartGit lets you see those concepts.
- Im_a_throw_away 10y agoI'm curious: What are the best free GUI for Git?
- Xantier 10y agoSourcetree, if you are not on Linux like me :(
- cx1000 10y agogitk - it's built into git, and supplements (not replaces) the command line. It does tree visualization and diffs between commits.
- robterrell 10y agoI'm a fan of tig on the command line and Gitbox (Mac GUI).
- junke 10y agoMagit
- DiThi 10y agoI'm surprised nobody mentioned Git Extensions yet. My absolute favorite Git UI, better than my previously favorite git-cola. https://gitextensions.github.io/ https://gitextensions.github.io/
- atsaloli 10y agoI'm a big fan of GitLab. Clean design, intuitive interface, many features. Disclaimer: I'm now a GitLab authorized training partner and reseller. The community edition is free. :)
- patrickthebold 10y agoInteresting. I've always been too scared of git GUIs to seriously try them out. The fear being I will somehow mess up the repo by using the GUI wrong.
- Zardoz84 10y agoI feel more comfortable and faster using git commands that a GUI.
- davidmpaz 10y agoI am surprised that somebody claim that has messed up a git repo. Since I started using git, I haven't ever messed up with my code. I always use git on the command line. Regarding GUI tools I like to avoid them, for me is too much noise. People get lost most of the time because they don't know what the tool is doing. After all is just one more layer on top of git core tool per se (aka, what you have in command line).
- xbryanx 10y agoSure, it's harder to screw up. But, dang it's just so remarkably slow. If you're used to the commands from the keyboard, where you're likely already typing from your editor...can't imagine going back to the GUI.
- emodendroket 10y agoI've never really screwed it up that badly using the command line either. I don't know what these people are trying to do that they constantly mess up their repository so bad they can't fix it. Perhaps being too obsessed with having a perfect commit history.
- base698 10y agoI've seen repos completely borked because the gui kept a merging and pushing in the background. This was after spending a lot of time removing binaries from a repo and not being able to figure out how the same binaries kept ending up back on origin.
- hellofunk 10y agoI agree, and while I have not tried the other apps mentioned here, I do rely extensively on Atlassian SourceTree client for Mac and find it very useful.
- busterarm 10y agoI've worked with a guy who only uses GUI tools for Git and he's supposed to be a senior dev and doesn't know how to resolve a simple merge conflict and regularly wipes out other peoples' work with whatever he's doing with the tool. No thanks.