Gitx GitX

I am a command-line user myself, but on seeing high praise for GitX I thought I would take a look at it out of curiosity just to see how it looked.

I didn't "install" it as such; I just downloaded the zip, unpacked it, and double-clicked the app. I later trashed the app. (I was very impressed with the speed and the UI; it's just that I'm a command-line user when it comes to SCMs.)

I was somewhat surprised to see that by running GitX I had turned all of my Git repositories (well, all of those with a ".git" extension, generally clones of upstream projects) into unnavigable, double-clickable packages like the one shown in the screenshot that I will attach.

I understand the rationale (so that a user can double-click a repo and start viewing it in GitX), but it is a very annoying behaviour, IMO, for two reasons: firstly, it is very easy to accidentally make this happen (just by running GitX once) without intending to make the change; and secondly, once done it is somewhat difficult to undo the damage, and non-obvious how one might go about this.

Might I suggest that this behaviour be made opt-in? ie. a preference along the lines of "Open .git repositories in GitX with double-click", with a clarification underneath or in a tool tip like "All directories with a .git extension will become bundles".

Or if not made opt-in, a button or some other means in the UI should be provided to undo the damage.

For anyone stumbling on this ticket who has suffered the same fate. Here are your possible workarounds:

(Temporary workaround.) Right-click or Control-click on your repo directory in the Finder and choose "Show package contents" to look inside it.

(Permanent workaround.) Rename directory from "repo.git" to "repo". Depending on whether you have the Finder set to show extensions or not, you may have to do this from the Terminal or from the "Show information..." window.

(Permanent solution.) If, like me, you were only taking a quick look at GitX, drag it to the Trash and empty the Trash. If you are lucky, the system itself will notice and immediately undo the damage done to the LaunchServices database. If you are unlucky, or you delete the app by some other means ("rm" in the Terminal, for example), then you'll have to rebuild the LaunchServices database yourself with the "/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister" tool.