The trial version of GitFinder is fully functional for 30 days. After that period, GitFinder will work with ONLY ONE git repository, the first one you browse into in Finder after launching GitFinder. All other git repositories will be ignored (no icon badges nor commands in the contextual and toolbar item menus).
Currently, there isn't a very strict license policy imposed. GitFinder doesn't check on how many Macs a single license is used; not by contacting our server, not by checking running instances in the local network, not by keeping any local reference to number of used licenses. Some reasonable usage would be one license on 3 - 5 Macs and we rely on people being fair enough not to abuse that.
There aren't any specific license packs (family, site, business) at the moment, but if the demand for those grow big enough, such licensing may be introduced as well.
No, there aren't such limitations. First of all, GitFinder is NOT a subscription ware and it will never be! Being categorized as a developer tool, we strongly believe GitFinder is in the software category, that should NOT be distributed through subscription.
We still stick to the old school licensing model; full price for the first purchase, upgrade price for major upgrade versions. Currently the next major version is still 2 - 3 years away.
Icon badges shown in Finder and provided by GitFinder are divided in two groups:
Here is the complete list:
- file is up-to-date (no changes)
- file is added to the working directory (unstaged), not yet tracked
- file is modified in the working directory (unstaged)
- file is deleted in the working directory (unstaged)
- file is renamed in the working directory (unstaged)
- file type is changed in the working directory (unstaged)
- file is added to the repository index (staged)
- file is modified in the repository index (staged)
- file is deleted in the repository index (staged)
- file is renamed in the repository index (staged)
- file type is changed in the repository index (staged)
- file is in the conflicted state
- file is ignoredIcon badges and menu commands in Finder are provided by a Finder Sync extension embedded in GitFinder. The first thing to check is if GitFinderSync extension is enabled. It should be automatically enabled the first time you launch GitFinder, but perhaps something went wrong with OS extension system. On macOS 13 Ventura and later (as of this writing, this DOES NOT APPLY to macOS 15 Sequoia, see a special note below), extension settings are buried deep inside System Settings application. Open System Settings application, select Privacy & Security in the sidebar on the left, scroll down completely the right pane, until you see Others: Extensions. Click on it and the right pane will change, revealing Added extensions at the top. Click on it and in the window sheet that appears there should be GitFinder listed, with Finder extensions checkbox, like it the picture below:
Make sure the GitFinder: Finder extensions checkbox is ticked, which means GitFinderSync extension is enabled.
On macOS 12 Monterey and earlier, extension settings are much easier to find, inside System Preferences application. Open System Preferences application and click on Extensions in the main pane. There should be Finder Extensions section in the list to the left of the window. Reveal Finder Extensions section and in the list that appears on the right there should be GitFinderSync extension listed, like it the picture below:
Tick the checkbox on the left of extension name to enable it.
SPECIAL NOTE for macOS 15 Sequoia: Apple removed the Finder Sync extensions configuration interface from System Settings in macOS 15 Sequoia. Managing these extensions is possible only using the command line tool pluginkit. To avoid using the terminal, you can use FinderSyncer, a small tool I created for this purpose. There is the whole story surrounding its creation, which you might be interested to read. It enables managing of Finder Sync extensions the same way as in System Settings/Preferences application, as shown in the picture below:
If GitFinderSync extension is enabled, but you still don't see any badges nor git menu commands while GitFinder is running, check if the extension is running as well. Open Activity Monitor application and see if the process named GitFinderSync is running. If it is not, then it wasn't started by the OS. GitFinderSync extension is started by the OS, not by GitFinder itself. In order to ensure reliable starting or the extension, GitFinder HAS to be installed in either /Applications (OS applications folder) or ~/Applications (your home applications folder). Installing GitFinder in any other location DOES NOT ensure successful start of the extension. It may work, but it also may not.
If GitFinderSync is running but you still don't see icon badges nor git menu commands, perhaps you forgot to add folders where your repositories reside into Repositories in GitFinder preferences. This has to be done due to a way Finder Sync extensions work (and partially due to GitFinder's sandboxed nature). Go to GitFinder > Preferences… > Repositories and add your repository folders, like it the picture below:
Note that you don't need to add to the list separate folder for each repository. If, for example, all your repositories are located in a single folder, you can add only that parent folder. GitFinder will look for repositories down the folder hierarchy.
If everything above is fine, and you still don't see icon badges (but you do see git menu commands), GitFinder extension may be colliding with another Finder Sync extension. This happens if your git repository folder is monitored by multiple Finder Sync extensions. In such case, please make sure GitFinderSync extension is "registered first". The easiest way to ensure this is to manage extensions in System Settings on macOS 13 Ventura and later (again, for macOS 15 Sequoia see the special note above and use FinderSyncer), that is in System Preferences on macOS 12 Monterey and earlier . Reveal Finder Sync Extension settings, just like explained above and uncheck/unregister all Finder Sync extensions (make sure they are Finder Sync extensions, not something else, like Sharing or Notifications o something else) except GitFinderSync. This is how it should look like on macOS 13 Ventura and later:
Or on macOS 12 Monterey and earlier:
Then relaunch GitFinder and make sure the icon badges are present. Then register/check back all extensions you unregistered previously. After this procedure, you should always see GitFinder icon badges, provided GitFinder is running and a particular current folder is monitored. This procedure needs to be repeated every time you get Finder Sync extensions collision, but doing it just once should suffice. This is all due to a bit sloppy job Apple did regarding more extensions monitoring the same folders and there's nothing we can do about it.
Finally, some system folders cannot be monitored by Finder Sync extensions. Such folders are iCloud Drive, and some subfolders of /System and /Library (system and system library folders). GitFinder cannot show contextual menu and toolbar item menu items for these unmonitored folders and folders and files inside their hierarchies. If your git repository is located inside those folders (which is highly unlikely), GitFinder cannot show icon badges nor offer git menu commands.
GitFinder integration is provided by a Finder Sync extension GitFinderSync, which primary function is integration with Finder. Hence, GitFinder doesn't integrate with other file managers for macOS.
Currently, GitFinder integrates with the following diff tools:
The following merge tools are supported:
In order to use supported tool, GitFinder's scripting support needs to be installed. The first time you try to use diff/merge tool from GitFinder, it will offer you to install scripting support. Just follow a single step procedure. After that, all installed tools from the lists above will automatically appear in the GitFinder > Git Configuration… > General.
GitFinder doesn't use git command line tool for its functioning, it solely relies on using a separate library for git operations. This means any kind of collision between GitFinder and any other client (including git command line tool) is not possible. You can use GitFinder with any other git client running at the same time.
In a sad case of wanting to get rid of GitFinder, it's easy as dragging its icon to the Trash and emptying the Trash. In a highly unlikely case of getting alert "The item “GitFinder” can’t be moved to the Trash because some of its extensions are in use", open Activity Monitor, find GitFinderSync process, select it and perform Force Quit on it. After that you'll be able to delete GitFinder.
Forgot your license key?
Feature request or bug report?
If you are on GitHub, the fastest way is to use GitFinder bug and issue tracker.
Not on GitHub or have a sales issue, bug report, feature request, feedback?
Please use the form below.
