๐ด FinderGit 0.24.0 โ update a fork that has drifted, right from the app
๐ด FinderGit 0.24.0 is out!
If you keep forks around, you know the moment: you open one, it's behind, and GitHub's one-click Sync refuses โ because you did some work of your own in there. Which is why you forked it in the first place.
FinderGit used to tell you that and stop. Now it just fixes it. โจ

A forked repository's Overview in FinderGit. The banner reads "53 behind ยท 1 ahead โ diverged" with an Update button beside it.
๐ Update, from the fork's banner โ merge to keep your commits where they are, or rebase to replay them on top. You choose, every time.
๐ It wires up the connection for you โ a clone of a fork has no link back to the original, which is why a plain fetch never had anything to fetch. FinderGit adds it on first use.
๐ It stops before pushing, on purpose โ after a rebase the next push needs a force, and that's your call, not the app's. It tells you which case you're in.
๐งน It won't quietly repoint a remote you set up โ if your upstream points somewhere unexpected, it stops and names both, instead of pulling in a stranger's commits under your parent's name.
A fork that's merely behind still gets the one-click Sync, which updates it on GitHub too โ it just isn't the only route any more.

The same banner for a fork that is only behind, where Sync sits on a split button alongside the local options.
โ Fixed: files with accents or non-Latin characters in their names couldn't be staged, unstaged or discarded.
At all. Now they can.
Free, universal binary, macOS 15+, signed and notarized.
๐ Try it / see what's new: https://findergit.app
What's the fork you've been putting off updating? ๐


Replies