Hey everyone Small release with a big "why wasn't this always here" energy.

Every commit now unfolds.

Click the chevron on any commit and the files it touched appear underneath status letter, path, the old name on a rename, per-file line counts. Click a file and you get that commit's diff for that one file. Read-only, nothing to accidentally stage. Deleted files open too, because what got removed is usually the interesting part.

FinderGit 0.28.0 is out, and it finally answers the most ordinary interruption there is.

You're halfway through something. The thing you actually need to do is the other thing. A commit would be wrong you're not finished, and a commit you have to undo is worse than none. You just want to put this down for a minute.

Hey everyone

FinderGit 0.27.1 is out, and Codeberg is now a first-class citizen in it.

Stop means stop. A Fetch, Pull or Push that is dragging? Three seconds in, its button becomes a stop control. Click, done the Git process underneath actually ends, it is not just the app looking away.

Why three seconds? So a double-click on Fetch does not cancel the fetch you just started.

Last week's release added a panel that tells you whether a slow afternoon is FinderGit's fault or GitHub's. It shows four services and never puts a reassuring green tick on your screen.

So: what if you want the rest? Now there's a Details link straight to GitHub's own status page every service, the 90-day uptime, the full timeline.

FinderGit 0.25.0 is out is it you, or is it GitHub?

You know the afternoon. A fetch that normally takes a second just sits there. A column comes up empty. So you quit the app, relaunch it, check your Wi-Fi and it was GitHub all along.

FinderGit now tells you which it is.

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.

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.

The advice used to be simple: read the diff, don't run code you don't trust, let your antivirus handle the rest. That quietly stopped being enough.

Two things changed the shape of the attack:

A git gc tells you a repo is big. 0.14 tells you why.

Analyze history (in the Maintenance tab) find out if a stale branch or an oversized clone is weighing a repo down: it ranks the heaviest branches and estimates what you could reclaim. Read-only it never changes a thing.