HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
brotherbard
gitx
Objective-C2010–2011
brotherbard / gitx

gitx

Experimental fork of Pieter's nice git GUI for OS X. Includes: sidebar, fetch, pull, push, add remote, merge, cherry-pick, rebase, clone, clone to. Mac OS X 10.5+ (see wiki for screenshot)

10Distinct people
10Mentions
1Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Experimental fork of Pieter's nice git GUI for OS X. Includes: sidebar, fetch, pull, push, add remote, merge, cherry-pick, rebase, clone, clone to. Mac OS X 10.5+ (see wiki for screenshot)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Brotherbard's fork has a bunch of additional features and I've found it to be pretty stable. I use it daily and highly recommend it. https://github.com/brotherbard/gitx

sant0sk1 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month10 dated mentions

Observed mentions: 2010-03-25 20:05:59 UTC to 2011-06-13 04:36:13 UTC.

01232010-03-01 00:00:00 UTC to 2010-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 20102010-04-01 00:00:00 UTC to 2010-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-05-01 00:00:00 UTC to 2010-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2010-06-01 00:00:00 UTC to 2010-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-07-01 00:00:00 UTC to 2010-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-01 00:00:00 UTC to 2010-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-09-01 00:00:00 UTC to 2010-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-10-01 00:00:00 UTC to 2010-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 20102010-11-01 00:00:00 UTC to 2010-12-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2010-12-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-01-01 00:00:00 UTC to 2011-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-01 00:00:00 UTC to 2011-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-03-01 00:00:00 UTC to 2011-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-04-01 00:00:00 UTC to 2011-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-05-01 00:00:00 UTC to 2011-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-06-01 00:00:00 UTC to 2011-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 2011

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20102010-03-01 00:00:00 UTC2010-04-01 00:00:00 UTC101
Apr 20102010-04-01 00:00:00 UTC2010-05-01 00:00:00 UTC000
May 20102010-05-01 00:00:00 UTC2010-06-01 00:00:00 UTC101
Jun 20102010-06-01 00:00:00 UTC2010-07-01 00:00:00 UTC000
Jul 20102010-07-01 00:00:00 UTC2010-08-01 00:00:00 UTC000
Aug 20102010-08-01 00:00:00 UTC2010-09-01 00:00:00 UTC000
Sep 20102010-09-01 00:00:00 UTC2010-10-01 00:00:00 UTC000
Oct 20102010-10-01 00:00:00 UTC2010-11-01 00:00:00 UTC101
Nov 20102010-11-01 00:00:00 UTC2010-12-01 00:00:00 UTC303
Dec 20102010-12-01 00:00:00 UTC2011-01-01 00:00:00 UTC000
Jan 20112011-01-01 00:00:00 UTC2011-02-01 00:00:00 UTC000
Feb 20112011-02-01 00:00:00 UTC2011-03-01 00:00:00 UTC101
Mar 20112011-03-01 00:00:00 UTC2011-04-01 00:00:00 UTC101
Apr 20112011-04-01 00:00:00 UTC2011-05-01 00:00:00 UTC101
May 20112011-05-01 00:00:00 UTC2011-06-01 00:00:00 UTC000
Jun 20112011-06-01 00:00:00 UTC2011-07-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
GitX --------------- # What is GitX? GitX is a gitk like clone written specifically for OS X Leopard and higher. This means that it has a native interface and tries to integrate with the operating system as good as possible. Examples of this are drag and drop support and QuickLook support. # Features The project is currently still in its starting phases. As time goes on, hopefully more features will be added. Currently GitX supports the following: * History browsing of your repository * See a nicely formatted diff of any revision * Search based on author or revision subject * Look at the complete tree of any revision * Preview any file in the tree in a text view or with QuickLook * Drag and drop files out of the tree view to copy them to your system * Support for all parameters git rev-list has # License GitX is licensed under the GPL version 2. For more information, see the attached COPYING file. # Downloading GitX is currently hosted at GitHub. It's project page can be found at http://github.com/pieter/gitx. Recent binary releases can be found at http://github.com/pieter/gitx/wikis. If you wish to follow GitX development, you can download the source code through git: git clone git://github.com/pieter/gitx # Installation The easiest way to get GitX running is to download the binary release from the wiki. If you wish to compile it yourself, you will need XCode 3.0 or later. As GitX makes use of features available only on Leopard (such as garbage collection), you will not be able to compile it on previous versions of OS X. To compile GitX, open the GitX.xcodeproj file and hit "Build". # Usage GitX itself is fairly simple. Most of its power is in the 'gitx' binary, which you should install through the menu. the 'gitx' binary supports most of git rev-list's arguments. For example, you can run `gitx --all' to display all branches in the repository, or `gitx -- Documentation' to only show commits relating to the 'Documentation' subdirectory. With `gitx -Shaha', gitx will only show commits that contain the word 'haha'. Similarly, with 'gitx v0.2.1..', you will get a list of all commits since version 0.2.1. # Helping out Any help on GitX is welcome. GitX is programmed in Objective-C, but even if you are not a programmer you can do useful things. A short selection: * Create a nice icon; * Help with the Javascript/HTML views, such as the diff view; * File bug reports and feature requests. A TODO list can be found on the wiki: http://github.com/pieter/gitx/wikis/todo
Read the full README on GitHub

What Hacker News says

10 sources
It's not a "people" issue. How does one discern the canonical source of a package on GitHub? Take GitX as an example: The "top parent" project: https://github.com/pieter/gitx Andre Berg's fork: https://github.com/andreberg/gitx The Brotherbard fork: https://github.com/brotherbard/gitx Which is "the project"? The answer is all of them AND none of them. That's the nature of GitHub. Zed's point is that for a sysadmin, all this obscurity is unacceptable. Having a canonical source for a package is important. That source should obscure away who the actors are making the package happen. If Pieter wants to hand the project off to Andre, who in turn hands it off to Nathan, that's great, but the sysadmin doesn't really want to track that for every package he/she installs on their server. That is why launchpad is better for sysadmins. Not because it
Read the rest
is better in any general sense. Just because it meets a different set of needs. These are not criticisms of GitHub, these are statements of the reality. The closest thing GitHub has to a "project" abstraction is the organization: https://github.com/blog/674-introducing-organizations One could, conceivably, create an organization to manage a project's code, but that doesn't address all of the other package ecosystems that Launchpad executes more deftly.
In Zed Shaw: Launchpad vs. Github/SysAdmin vs. Coder
You're quite wrong. GitX is available at https://github.com/brotherbard/gitx/downloads (Get the experimental branch) Git Tower is available at http://www.git-tower.com/ Textmate has a GIT Bundle at https://github.com/jcf/git-tmbundle (It's quite good, but maybe not for designers). And Giggle (http://live.gnome.org/giggle). Windows is the only OS lacking a good client, but I use GitX for Mac every day, as do the less technical "devs" at our Startup.
In Designers, how do we get you guys to contribute to open source projects?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.