git has always had an answer for that. FinderGit did not.

Stash, where the work already is

0.28.0 puts a Stash… button in the working-tree tab, beside Stage All and Discard All. It belongs there because it is the third answer to the same question — what do I do with these changes right now — and the only one that is neither destructive nor a commitment.

Give the stash a name, or leave the field empty and let git name it after your last commit. Untracked files come along, so what you get back is a genuinely clean tree rather than a half-tidied one.

Everything you have set aside is listed under the commit box, collapsed until you want it.

Each entry carries the branch it came from and how long it has been waiting — because the stash that matters is the one you forgot about, and “last month, on a branch you have since deleted” is the sentence that tells you what to do with it. When git wrote the description rather than you, a quiet Automatic badge says so, so a subject you never typed does not read as one you chose.

Three things you can do with any of them: bring the work back and keep the stash, bring it back and remove it, or throw it away — that last one behind a confirmation that says plainly the changes are not applied first.

And when it goes wrong

If bringing a stash back hits a conflict, the conflict lands in your files and the stash stays put. Nothing is lost, the entry is still on the list, and you can try again once you have resolved it.

On a clean tree, FinderGit tells you there was nothing to stash rather than reporting success for something that did not happen. That direction matters: the other way round leaves you walking away believing your work is safe.

All of it is translated along with the rest of the app — Italian, French, German and Spanish, dates and ages included.

A smaller thing, and one fix

Removing a root folder used to be something only the pointer could do. It has a menu item now, File → Remove Root Folder, acting on the folder selected in the window you are actually using — so it does the right thing with more than one window open.

And one fix worth naming, because you may have seen it without knowing what it was: when a git action failed, the red warning in the action bar could vanish a second or two later. It happened on exactly the actions that had changed something on disk, because re-reading the repository overwrote the message with “nothing wrong here”. The failure now outlives every refresh, which is what “Last action failed” always claimed to mean.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

I had that afternoon on the 4th of August. FinderGit was the app I was blaming.

It wasn’t FinderGit. GitHub was having a bad day. But there was no way to know that from inside the app — because every symptom of GitHub struggling looks exactly like FinderGit being broken. A fetch that crawls. A repository column that comes up empty. A dashboard that never settles.

0.25.0 closes that gap.

The Overview now tells you whose problem it is

There’s a new GitHub connection panel, and a GitHub card in the stats row above it. Between them they answer two different questions.

The card shows how quickly your own requests are actually coming back — measured on your machine, from the calls FinderGit is already making. The panel shows what GitHub says about itself, for the four services FinderGit actually depends on: Git operations, API requests, Issues and Pull Requests. If there’s an open incident affecting one of them, its name and GitHub’s latest official update appear right there, with a link to the full story.

Only those four, and that’s deliberate. An outage of something FinderGit never touches isn’t news to you, and a warning that fires on everything is a warning you learn to scroll past.

It won’t tell you GitHub is fine when it can’t check

This is the part I care most about, and it’s the reason the feature isn’t what I first set out to build.

When I went to check GitHub’s own incident history for the 4th of August — the day this all started — there was nothing there. Entries on the 3rd, entries on the 5th, and a hole exactly where my bad afternoon had been.

So if I’d built the obvious thing — read the status page, show a green tick when it says all is well — the app would have shown me a reassuring green while my fetches crawled. That’s worse than showing nothing at all, because now the app is telling me with authority that GitHub is fine, which sends me right back to blaming my own machine.

So the number that leads is the one measured on your side. A status page can only ever report what somebody decided to declare. Your own requests don’t need anyone’s permission to be slow.

And when something genuinely can’t be established — the status page is unreachable, a service can’t be read — it says Unknown. In grey, deliberately hard to mistake for green.

Waiting is no longer a mystery either

Past three seconds, a running Fetch, Pull or Push shows how long it’s been going, right on the button. A spinner tells you something is happening. It doesn’t tell you whether that something is working or wedged, and when a server is answering slowly that’s the only question you have.

Underneath, those three used to be allowed five minutes before giving up — a limit that made sense for a Git process stuck on your own machine, and no sense at all for one waiting on a server. While any action runs, every action on that repository is greyed out, so a slow remote could leave a repository unusable for five minutes at a stretch. That’s much shorter now. A first clone, which legitimately takes minutes on a big repository, keeps its own generous allowance.

Opening the Overview on a large workspace also used to bog the whole app down: every repository asked “is GitHub reachable?” at the same moment, and none of them noticed the others were already asking. Now they share one answer.

One more, caught the day before release

This one is my favourite, because it’s the feature getting its own medicine.

If your access token had been revoked, every request to GitHub would fail — and the new panel counted those as GitHub’s failures. It would have told you “Your GitHub requests are failing” when the problem was sitting in your keychain. A feature built specifically to stop you blaming the wrong thing, blaming the wrong thing.

A request that was refused is now kept separate from a request the server couldn’t answer. Only the second kind counts against GitHub.

The new panel is fully translated into Italian, French, German and Spanish, plural agreement included.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Until now FinderGit would tell you that and stop. The banner said the fork had diverged and that you’d need to sync from upstream manually, which is a polite way of saying go open a terminal. That was the honest answer at the time, because a fast-forward genuinely can’t apply once both sides have moved. But “here’s a thing you can’t do from here” is a strange thing for an app to say about the situation it’s best placed to fix.

So now it fixes it.

Update, from the banner

When a fork has drifted, the banner grows an Update menu with two ways forward:

• Merge keeps your commits where they are and records a merge commit.

• Rebase replays your commits on top, for a linear history.

FinderGit sets up the connection to the original repository the first time — a clone of a fork doesn’t have one, which is exactly why a plain fetch never had anything to fetch — then brings the parent’s changes in.

A fork’s Overview showing it has diverged, with the Update menu beside it

Both options are offered every time, rather than quietly following whatever your Pull preference happens to be. Choosing merge once here shouldn’t change how the rest of your repositories behave.

Two things it deliberately doesn’t do

It doesn’t push. After a rebase your history has been rewritten, so the next push needs a force. That’s a decision with consequences for anyone else who has that branch, and it isn’t one to take on your behalf. FinderGit tells you which situation you’re in when it finishes, and leaves the push to you.

It doesn’t quietly repoint a remote you set up. If your clone already points somewhere for its upstream, and that somewhere isn’t the fork’s parent, FinderGit stops and names both instead of pulling in commits from a repository you didn’t mean. A sibling fork shares enough history that the merge would have worked — and you’d have had no way of knowing.

The one-click Sync is still there for a fork that’s merely behind, since that also updates the fork on GitHub itself. It just isn’t the only route any more — it now shares a split button with the local options, which matters if your token can’t push to the fork, or you never set one up.

A fork that is only behind, where Sync sits on a split button alongside the local merge and rebase options

Accented filenames

A quieter fix, but a real one. If any of your repositories hold files with accents or non-Latin characters in their names — café.txt, Cyrillic, Japanese, an emoji — staging, unstaging and discarding them silently did nothing. The name came back from Git in an escaped form that FinderGit handed straight back without unescaping, so the action was applied to a file that didn’t exist.

It affected every such filename, not an unlucky few. If you’ve ever clicked Stage on a file and watched nothing happen, this was probably why.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

There’s a particular kind of stuck that every one of us has hit. You come back to a repository, the status says five commits ahead and eight behind, you press Pull… and nothing happens. You press it again. Still nothing.

It isn’t your imagination, and it isn’t the button. When your branch and the remote have both moved on, Git refuses that pull outright — there is no single right answer, so it declines to guess and changes nothing at all. FinderGit did report the refusal, technically: as a wall of Git’s own output hidden behind a small red triangle. Which is a polite way of saying it didn’t help.

0.23.0 is about that dead end, and about everything sitting behind it.

It says what’s wrong, in words

When a branch has drifted both ways, a strip now appears above the action bar and names the situation — Diverged from origin/main, with both counts — followed by the only two things that actually resolve it: Merge or Rebase. The Pull button turns into a menu with the same choice, and if a pull or push already failed, those same two options wait inside the error popover. The fix is one click from the sentence explaining it.

There’s also a new Pull strategy setting. Pulling now behaves identically on every machine you own, because FinderGit states the strategy every single time instead of inheriting whatever your Git config happens to hold. The default is the cautious one: advance the branch when there’s nothing to merge, and stop and ask when there is.

When it stops halfway, it tells you

Git integrates what it can on its own and stops at the first real conflict, leaving the repository half-finished. Until now that state was invisible: the app kept offering a Pull that could only fail.

Now the strip switches to it. It names what’s open, counts the files still in conflict, and gives you Finish and Abort right there. Pull and Push go quiet, with a tooltip saying why. And it doesn’t matter who started the operation — begin a merge in your terminal and the app notices on its own.

In the changes list, unmerged files are tagged CONFLICT and carry a Mark Resolved action, which is precisely what Git wants from you next.

The one that surprised me

While building this I looked at one of my own repositories: 78 commits ahead, 78 behind. Symmetrical, alarming, and completely misleading — every one of those 78 was already on the remote. Months earlier I had rewritten the history and force-pushed it, and this clone had simply kept the older copy. Merging would have duplicated all 78 commits, and Git would have refused anyway.

An ahead/behind count cannot tell those two situations apart, so FinderGit now compares the actual changes rather than the commit identities. It tells you which case you’re in: whether your local commits carry real work, or are a rewritten echo of what’s already published — and in the second case it puts the action that fixes it in front of you.

If you work from two machines, you have almost certainly seen this shape without knowing what it was.

Smaller things you’ll notice

Git’s everyday failures now come with one line of plain language above the raw output: a rejected push, conflicts still open, local edits in the way, a missing upstream, credentials it couldn’t get, a host it couldn’t reach. A Diverged smart view in the sidebar and a count in the status bar gather the repositories that need a decision. And the status tooltip no longer advises “pull then push” — the one sequence that cannot work in the state it was describing.

All of it speaks your language: Italian, French, German and Spanish, following macOS.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

0.22.0 is about closing that little gap.

See what’s coming, before you pull

The Commits tab now opens with an “Incoming” section whenever a repository is behind its upstream. It lists the exact commits your next pull will bring in — each marked with a small ↓, sitting right above your own local history. So you’re no longer told just that you’re behind; you can read what you’re about to receive, decide whether now is the moment, and pull with your eyes open. It reads entirely from what’s already on your disk, so opening it costs nothing — and the section quietly disappears the moment you’ve pulled.

Incoming commits in the Commits tab

Proof your repos are current

Every repository’s detail bar now shows when it was last fetched — a plain “Last fetched 3m ago”. FinderGit has been quietly fetching your repos in the background for a while; now you can actually see it happening, so “behind by 2” always means behind as of a moment ago, not behind since who-knows-when.

Both are fully localized — Italian, French, German and Spanish, following your macOS language.

That’s the release: two small things that, together, make “behind” mean something you can act on.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

0.21.0 fixes that. Turn on Discover nested repositories and FinderGit counts the repos nested inside your repos — across every count, Smart View, and the Overview.

It’s off by default, because it changes your totals and you should be the one to ask for it. When you want it, it’s one flip away — from Settings, the View menu (⌘⇧N), or a new toolbar toggle right next to Refresh. The Overview even tells you when nested counting is on. And it stays sensible: bounded by your scan depth and excluded folders, and submodules are never counted.

Nested discovery on — the same workspace now shows 63 repositories

Two more things landed alongside it:

• A clearer Overview header — Clone from GitHub and Refresh are now grouped into one prominent control cluster, so the actions you reach for are easier to find.

• Full translations — everything new, including this update’s What’s New panel, reads naturally in Italian, French, German, and Spanish.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Faces, not just names. Every commit now leads with its author’s avatar, right where your eye lands first — exactly like the Issues and Pull Requests tabs already do. When there’s no photo to show, FinderGit draws a tidy coloured monogram from the author’s initials, so the column never looks empty.

Your releases and branches, at a glance. Commits that a tag or a branch points at now wear a badge — tags in gold, the branch you’re on in the accent colour, and remote-tracking refs in a calm grey. Jumping back to “where was v1.2.0 again?” is now a half-second glance instead of a squint.

Dates that speak your language. Relative commit times used to always read in English. Now they follow the app’s language — “3 settimane fa”, “il y a 3 semaines”, “vor 3 Wochen”, “hace 3 semanas”.

A home for all of it. A new Detail View section in Settings gathers how many commits the tab lists, plus switches to show or hide the avatars and the badges — whatever keeps your history readable for you.

All the new interface text is already translated into Italian, French, German, and Spanish.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

The Repository List — every repository you track in one sortable table

Meet the Repository List. It’s the new home view: every repository you track, laid out in one flat, sortable table — branch, status, ahead/behind, file count, and size, side by side. No more expanding folders to remember what’s where. Sort by whatever you’re chasing, click a column header, and the whole fleet reorders.

The real shift is in the sidebar. Smart Views let you slice that list by live Git state in one click — everything with uncommitted changes, everything ahead of its remote, everything behind, dirty, or perfectly clean — each with a running count, so you can see at a glance that seven repos need a push before you even look. Right below, Filters slice by remote host: GitHub, GitLab, Bitbucket, or the ones that live only on your Mac.

Smart Views and Filters slice the list from the sidebar; the summary bar tallies the whole workspace along the bottom

And because the repositories you actually touch aren’t a random sample, there’s now Favorites — star your go-to projects — and Recents, which quietly remembers the ones you opened last, so they’re always a click away.

Along the bottom runs a summary bar: a live tally of the whole workspace — how many repositories, how many clean, how many dirty, how many ahead or behind, and the total size on disk. It’s the kind of number you never had before and suddenly can’t unsee.

Everything you already know is exactly where you left it: click any repository and the familiar detail panel opens with all eight tabs; double-click to drill into the Finder-style file browser. The new view sits on top of what was already there — it doesn’t replace a thing.

One more: the entire new interface speaks your language. FinderGit follows your Mac’s system language automatically in 🇬🇧 English, 🇮🇹 Italian, 🇫🇷 French, 🇩🇪 German, and 🇪🇸 Spanish — nothing to configure.

Update from within the app, or grab it below.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Update to 0.18.0 and — if your Mac runs in Italian, French, German, or Spanish — FinderGit simply greets you in your language. No setting to hunt for, no restart dance: the whole app follows your macOS system language, from the file browser columns to every menu, dialog, tooltip, and the Settings window.

It’s the kind of change you feel more than you read about: “4 of 7 clean” becomes “4 su 7 puliti”, the update prompt speaks your language, and even the little “What’s New” panel that pops up after an update now arrives translated.

A few details we sweated so you don’t have to:

• Counts read correctly everywhere — “1 commit” and “2 commits” inflect the right way in every language, not just English.

• Git stays git — commit, push, fetch, stage: the terms you type every day keep their names, in every language, on purpose.

• Prefer English? Nothing changes unless your Mac’s language is one of the new four.

This release also lays the rails for more languages — reply and tell me which one you’d like next.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

A small one this time, but one of those fixes that quietly removes a daily papercut.

If you keep a folder of projects — especially the kind where a repository lives inside another repository you track — you’ve probably seen the Branch column sitting empty, just a dash, until you clicked into each repo to wake it up. As of 0.17.1 that’s gone: open your list and every repository shows its branch and its status straight away. No clicking, no waiting.

It keeps up with you now, too. Fetch a handful of repos at once, commit, or stage some changes, and the Branch, Status and Changes columns update right there in the list instead of going stale until you reopened them. The Refresh button reaches those nested repositories as well.

That’s the whole release — no new buttons to learn, just the list telling you the truth the moment you look at it.

As always, FinderGit will offer the update automatically, or you can grab it from the releases page.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Right-click any repository and pick Open on GitHub — it opens that repo’s page in your browser. It’s also a button on the Overview tab, so the repo’s web page is always one click away.

The repo context menu, with Open on GitHub

The Overview tab, with the Open on GitHub button

Issues and Pull Requests, too

The Issues and Pull Requests tabs each got their own Open on GitHub button that opens the full list online — handy when you want the filters, search, or closed items the in-app list doesn’t show. (And as before, clicking any single issue or PR jumps straight to it.)

Issues tab — New Issue, Open on GitHub, Refresh

Pull Requests tab — Open on GitHub in the header

It follows your host

If a repository lives on GitLab or Bitbucket instead of GitHub, the button knows — it reads Open on GitLab / Open on Bitbucket and opens the right page. It only shows up when there’s actually a remote to open, so it never gets in the way of a local-only folder.

That’s the whole release — a little less context-switching, a little more flow. FinderGit updates itself, so it’s already on its way to you.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Last issue I showed you the big picture. This one zooms into the feature that started the whole app: live Git status, right in the file list.

Picture your projects folder in Finder. You see names and dates — but not which repo has uncommitted work, which one you forgot to push, or what branch you’re on. To find out, you open a terminal and run git status, project by project.

FinderGit shows it all as columns. Each repo gets its current branch, a clean, dirty, or unpushed status, and an ahead/behind counter: ↑2 means two commits waiting to push, ↓1 means one to pull, ↑2 ↓1 means both. Hover for the details.

It stays current as you work, and an optional background fetch keeps those ahead/behind numbers honest without you lifting a finger.

Because they’re real columns, you can sort by them. Sort by status and every repo that needs attention floats to the top — your morning triage in a single glance. And for repositories hosted on GitHub, you also get columns for open issues, pull requests, and stars.

No terminal, no opening each project one by one. You just look.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

A short note on a few improvements that just landed in FinderGit. No big new features this time — just the kind of polish you feel every time you open the app.

Your Mac can relax now

If you ever opened Activity Monitor and noticed FinderGit using a slice of CPU while it was just sitting there doing nothing — that’s gone.

The account dashboard had a tiny animation that never quite stopped, quietly keeping your Mac busy in the background. Now the app goes properly idle when you’re not using it. The nice side effect: everything feels more responsive, including the “Check for Updates” window, which used to drag for the same reason.

Your battery and your fans will appreciate it.

Quick Look now follows you

FinderGit lets you hit the Space bar to preview a file, just like in Finder. If you keep more than one window open, that preview now opens in the window you’re actually working in — not in every window at once.

It’s a small thing. But it’s exactly the kind of detail that should just work, and now it does.

A little quiet plumbing

There’s also some under-the-hood tidying: when a Git or GitHub action can’t reach a server, it now gives up quickly instead of lingering in the background. You’ll never see it directly — the app just stays out of its own way.

That’s it for this one — short and sweet. As always, FinderGit keeps itself up to date, so you’ll get these changes automatically the next time it checks.

Thanks for using it 🙏

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Last issue: spotting which repos are dirty. This one: seeing exactly what changed inside them.

The usual routine is a context switch. You drop into the terminal for git diff, or fire up a separate diff tool, then find your way back. For a quick “what did I touch here?” that’s a lot of friction.

In FinderGit you just click the modified file. A colored diff opens in the panel, with line numbers and additions and removals highlighted the way you’d expect — readable, right next to the file tree.

It’s made for the quick pre-commit sanity check: glance at the diff, confirm it’s what you meant, and move on. No window juggling, no losing your place.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

We’ve seen status and diffs. The other half of the job is acting on them — and that normally means switching back to the terminal or a separate Git client.

FinderGit keeps it in the same window. The detail panel lists your changes alongside a commit form: stage or unstage files, write your message, and commit.

The global Fetch, Pull, Push, and Refresh actions sit docked at the bottom and stay reachable from every tab. So the whole loop — notice a repo is dirty, review the diff, stage, commit, push — happens without ever leaving FinderGit. You can switch branches from the app too.

Under the hood it drives your real git, so everything behaves exactly as it would in your terminal: same results, fewer keystrokes.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

We’ve all done it: a meaningful change, and the commit box still gets “wip” or “fix stuff” because writing a good message takes effort.

FinderGit can do the first draft. Stage your changes, ask it to generate, and it reads the diff and proposes a clear commit message — a concise summary plus the details that matter.

It’s a draft, not a dictator. The message lands in the commit box and you edit it before committing: keep it, tweak it, or rewrite it.

It’s free and needs no API key, and your diffs aren’t stored. Just stage, generate, and commit.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

If you juggle more than a couple of Git repositories, you know the dance: open Finder to find a project, switch to the terminal for git status, maybe jump to a Git client to see what changed, then back again. Your files live in one place and their Git state lives somewhere else — and your attention pays the toll on every switch.

I built FinderGit to close that gap. It’s a native macOS app that looks and feels like Finder’s list view, but every row knows about Git.

Browse a folder of projects and you immediately see, in sortable columns: the current branch of each repo, whether it’s clean, dirty, or unpushed, an ahead/behind counter (↑2 ↓1) so you can spot what needs a push or a pull, and — for repos hosted on GitHub — even open issues, pull requests, and stars.

No terminal, no context switch. Click a modified file and a colored inline diff opens right there. Need to act? Stage, commit, push, pull, fetch, or switch branches without leaving the window.

That’s the elevator pitch — but FinderGit has grown a lot of small, deliberate touches that are easy to miss. That’s exactly what this newsletter is for.

This is the start of a series. Each issue I’ll zoom into one feature — the live status columns, the inline diff viewer, one-click Git actions, AI-generated commit messages, GitHub integration, repo maintenance, and more. Short reads, one idea at a time.

FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.

FinderGit for macOS — Website: https://findergit.app · Download: https://findergit.app/download

Thanks for being here. If you manage more than one Git repository, you already know the daily friction: Finder shows your files but none of their Git state, the Terminal gives you status one repo at a time, and full Git GUIs are powerful but heavy for a quick glance.

FinderGit exists to close that gap. It’s a native macOS app that puts all your repositories in one window — branch, clean/dirty/unpushed state, changed files, and diffs, updated live. No app switching, no terminal round-trips, no repos hiding in plain sight as ordinary folders.

This newsletter is where that story unfolds. Here’s what you can expect:

• Release notes that actually explain things — what changed, why it matters, and how to use it.

• Behind-the-scenes — the design decisions, the SwiftUI details, and the occasional dead end.

• Practical Git tips — small workflow improvements you can apply whether or not you use FinderGit.

• What’s coming next — early looks at features like Repo Trust, AI commit messages, and the Overview dashboard.

FinderGit is free, native, and built for macOS 15+. If you haven’t tried it yet, you can download it here and see your whole workspace at a glance.

Welcome aboard — and thanks for following along.

— Giovambattista (Undolog)

Want a punchier subtitle, a more personal tone, or a version optimized as the very first “launch” email? Just say the word.