7 ms·
There's also Fork: https://git-fork.com/ https://git-fork.com/
by manigandham 7y ago
There's also Fork: https://git-fork.com/ https://git-fork.com/
- echelon 7y agoI'm really curious - why do people want a graphical git client? The command line exposes everything, and the model is simple and intuitive. I work in a very large monorepo, so it's not like I'm working in a git tree that isn't complicated.
- mandeepj 7y agofor a new person, it's almost impossible to get anything done with git command line
- OJFord 7y agoYou could say that about any tool, of course you have to spend some time to understand how to use it safely and effectively. 'for a new person, it's almost impossible to get anything done with a table saw'
- jstrong 7y agodo people say, "a table saw is simple and intuitive"?
- throwawaymath 7y agoI haven't heard anyone say that, but after thinking about it for a second I sure as hell would. A table saw is a lot easier to use than git.
- OJFord 7y agoWell on the face of it, it's a simple tool isn't it? It's a spinning saw blade, and surface(s) against which to rest the wood being cut. And I've never used one, but I'm sure it takes some learning, skill, and practice to get good cuts the way you need them, e.g. bang on 45deg all the way across for a 'mitred' corner joint. And it certainly needs learning, care, and attention to operate safely. I don't mean it to be an insensitive analogy - accidents involving table saws are obviously horrendously worse than those involving git.
- manigandham 7y agoMany people are visual. It's a lot easier to see changes, compare diffs, and generally follow the development branches through a GUI instead of through a command line.
- dabeeeenster 7y agoGit is famous for being unintuitive?
- OJFord 7y agoInfamous, and a more accurate description might be that discussions about git are well-known for quickly descending into discussions about whether or not it's intuitive and whether or not that matters since you use it every day you'll soon get it and no longer care that much how intuitive it is anyway.
- aclsid 7y agoJust give thanks that you did not have to work with the likes of CVS and such.
- cwojno 7y agoTry doing a merge with IntelliJ's 3-way merge UI. It's flippin' fantastic compared to roaming through the files and removing sections between >>>> and <<<<.
- philwelch 7y agoCommand-line git allows you to specify a mergetool, many of which are capable of three way merges.
- cwojno 7y agoThe point was convenience. I don't have to leave the IDE.
- chiefsucker 7y agoFor some people Unix is the IDE.
- randomidiot666 7y agoAs someone else mentioned here, the graphical merge tool in IDEA is extremely powerful. Plus keyboard shortcuts to all the main Git actions. It's overall more efficient. However I always use Git IDEA + Git CLI side by side.
- muzani 7y agoOne of the advantages is you can easily explore what changes were made and merge conflicts through the tool.
- amerine 7y agoI think most folks like a graphical merge tool, such as opendiff, or at least that's what I've been able to glean.
- chrisseaton 7y agoI like to drag and drop commits into an order I want when doing an interactive rebase.
- gdxhyrd 7y agoThat's easy with the TUI
- chrisseaton 7y agoDragging and dropping? Or do I have to rearrange the lines using a text editor?
- gdxhyrd 7y agoRearranging a line is 3 keystrokes in vim, which I use for that particular action, since it is perfect for that, rather than my normal GUI IDE.
- andybak 7y ago> the model is simple and intuitive I nearly spat out my drink. Git is many things but those aren't the first two words that would leap into my head.
- fwip 7y agoThe model is relatively simple, but the UI is a disaster. Which is exactly why people want better clients than the official git cli client.
- erklik 7y agoI find that it has too many magic commands built-in so no-one really gets to learn the under-side of what's actually occuring so when it eventually breaks like everything does, you have no idea what you did wrong. An example would be how the git pull command is basically a bunch of different git fetch and merge commands.
- OJFord 7y agoYes, but if it didn't exist people would say git's bad because everyone copies the same alias from StackOverflow, and it should just be built-in.
- gdxhyrd 7y agoGit model is simple. What is complex is the hundred features and commands it provides on top of that model.
- deepaksurti 7y agoGit is a great example of worse is better philosophy.
- okusername 7y agoThats exactly wHat GUIs are good for. Make infrequenlty used features and options accessible.
- mehrdadn 7y agoSay you want to find a commit that occurred around June three years ago, and look at what the repo looked like after that commit -- without checking out any files. How do you currently do it? For me, I just Right click -> TortoiseGit -> Show Log -> scroll -> Right-click -> Browse Repository. How long does it take you? For me it takes < 10 seconds (I just timed myself).
- gdxhyrd 7y agogit log, copy paste hash, git checkout If you have a dirty wd, stash. But, to be honest, I almost never perform that action, and when I do I use the web browser.
- mehrdadn 7y ago> git log, copy paste hash, git checkout You remember the hash of your June commit 3 years ago?? > But, to be honest, I almost never perform that action, and when I do I use the web browser. Web browser... for a local repo? Or do you mean you don't have a solution if your repo isn't on GitHub or you don't have an internet connection handy? (You should also time yourself on your web interface by the way.)
- gdxhyrd 7y ago> You remember the hash of your June commit 3 years ago?? ...which is what the git log above is there for. > Web browser... for a local repo? Or do you mean you don't have a solution if your repo isn't on GitHub or you don't have an internet connection handy? Yeah, local repo. You know, git is not GitHub. :) > (You should also time yourself on your web interface by the way.) Just paste the hash commit in the HEAD selector or even in the URL.
- manigandham 7y ago> "when I do I use the web browser" So a graphical interface then? I'm sure you can see why using a GUI for other functions is just as useful.
- 7y ago
- hota_mazi 7y agoI wonder the opposite thing: why do people try to use git in a terminal? Its output is so rich and complex that it's impossible to make it legible outside of a real GUI, with graphics and colors.
- danielbarla 7y agoI think the main advantage of GUIs in general is a contextual, curated explorability that is often lacking in CLI tools. The GUI is stateful, allows the user to click on things and prod it, and hopefully shows the most frequently used features for that context. This allows even complete newbies to be productive almost immediately. For something like git, the slightly more visual representation is a benefit to many, too. I'm not here to knock CLIs, there are a set of tradeoffs to be made, and CLIs win in many cases (flexibility, scriptability, being able to copy snippets you frequently use, etc). The above does tend to hold true, however.
- kelsolaar 7y agoI work on a lot of repositories, having a GUI makes it really easy to change context and getting up-to-speed quickly.
- snypox 7y agoSwitched to Fork from SourceTree, never looked back.