🌿 FinderGit 0.23.0 — Pull that doesn't give up on a diverged branch

🌿 FinderGit 0.23.0 is out — and it fixes the most quietly infuriating thing in the app.

You know the moment: five commits ahead, eight behind, you press Pull… and nothing happens. Press it again. Still nothing. That's not the button — Git refuses that pull outright, because there's no single right answer, and it won't guess.

So now FinderGit says it out loud:

⚖️ It names the problem. A strip above the actions tells you the branch has diverged, from what, by how much — and offers the two things that actually fix it: Merge or Rebase. Same choice inside the error popover, so the fix is one click from the explanation.

🛠️ A stopped merge is no longer a mystery. When Git halts on a conflict, the strip says what's open, how many files are still fighting, and gives you Finish or Abort. Even if you started that merge in your terminal.

🔍 It can tell a rewritten history from real work. ↑78 ↓78 looks like two piles of commits. Often it's one history rewritten and force-pushed — and merging that duplicates every single commit. FinderGit compares the actual changes, not the commit IDs, and tells you which case you're in. (Found this on my own repo while building it. 78 for 78. All duplicates.)

🏷️ Conflicts get labelled where you work, with a Mark Resolved action that does exactly what Git wants next.

All of it in Italian, French, German and Spanish, following macOS. Free, universal, notarized, macOS 15+.

👉 Try it / see what's new:

What's the most confusing Git state your tools have ever shown you? I'd love to make that one legible next 🌿

3 views

Add a comment

Replies

Be the first to comment