Skip to main content

Git GUI client for Linux


Which is the best gui client on Linux for Git.



Update: After checking out all of the GUIs mentioned here,



git cola seems to work well for committing/pushing



gitk seem to work the best for examining history and



giggle is awesome for watching the diffs.



I use command line for committing, web trac interface for viewing history, in a rare occasions, and accept giggle as giggle is what, I think, one needs as a desktop git gui, with occasional git cola and gitk .


Source: Tips4allCCNA FINAL EXAM

Comments

  1. Take a look at "Graphical Interfaces" section of InterfacesFrontendsAndTools page on Git Wiki. There you have mentioned:


    gitk - graphical history browser, in Tcl/Tk, distributed with Git (usually in gitk package)
    git gui - graphical commit tool, in Tcl/Tk, distributed with Git (usually in git-gui package)
    QGit - uses Qt toolkit
    Giggle - uses GTK+ toolkit
    git-cola - uses PyQt4
    gitg - GTK+/GNOME clone of GitX
    tig - text mode interface for git, is GUI and pager, uses ncurses

    ReplyDelete
  2. There is also SmartGit, it is very newbie friendly.

    ReplyDelete
  3. Check EGit, the git plugin for Eclipse. It's still in incubation, but it looks promising. You can see how it looks in the user guide. Here are a few screenshots to wet your appetite:


    Repository Exploring:


    New files:


    Commit Window:


    History View:

    ReplyDelete
  4. Actually there is a GUI client for Git (and I bet you'll never guess it's name), Git-GUI.

    If your using a Debian-based distro of Linux (eg. Ubuntu) you can install it by typing this:

    sudo apt-get install git-gui

    ReplyDelete
  5. There's a mind-blowing large list of interfaces, including GUIs (36 of them!) and other front-ends here:
    https://git.wiki.kernel.org/articles/i/n/t/Interfaces,_frontends,_and_tools.html

    ReplyDelete
  6. As far as I'm aware, there aren't many GUI clients for git on Linux. git-gui is the only one I can think of off the top of my head.

    Git Cola also looks interesting, though I haven't personally used it.

    Also, depending on who you talk to, some people consider GitHub a git GUI of sorts. I won't argue the point, but I can say from personal experience that it is a useful tool/service.

    ReplyDelete
  7. Another GUI client is qgit. I've only used it for browsing repositories so far, though. Despite from that I found git-gui to be the one I like best.

    ReplyDelete
  8. I can recommend git cola for committing and giggle for examining commits and branches. I also tried Gitg but it seems to be rather unstable.

    git cola has frozen on some occasions and seems to be slow on large commits. Large commits are lightning fast on the command line.

    ReplyDelete
  9. For linux you can use SmartGit. Install as Non commercial use download
    SmartGit

    For windows this will be helpful. to download
    Git extensions

    ReplyDelete
  10. For those who do not like editing the list of commits during "git rebase -i" by hand i can recommend qgrit.
    (Qt git rebase --interactive tool)

    It allows you to graphically reorder commits and choose actions from a combo box.

    For a list of features/screenshots see:
    https://github.com/qgrit/qgrit/wiki

    This shameless plug was sponsored by the author of qgrit...

    ReplyDelete
  11. gitk + git-gui

    git-gui usage: git gui

    ReplyDelete
  12. If you are an Emacs user, magit is a good option although it's more a set of useful keybindings than a GUI proper.

    ReplyDelete
  13. I've decided to limit myself to gitk and git gui (and the command line of course). The reason is that they are powerful enough (I was surprised how complete git gui was) and they run on all platforms, which is often useful.

    I have git k aliased to gitk -all

    ReplyDelete
  14. RabbitVCS (with an interface much like TortoiseSVN) supports Git now.

    http://www.rabbitvcs.org/

    ReplyDelete

Post a Comment

Popular posts from this blog

Wildcards in a hosts file

I want to setup my local development machine so that any requests for *.local are redirected to localhost . The idea is that as I develop multiple sites, I can just add vhosts to Apache called site1.local , site2.local etc, and have them all resolve to localhost , while Apache serves a different site accordingly.