Skip to content

FinderGit 0.31.0

Latest

Choose a tag to compare

@gfazioli gfazioli released this 10 Sep 05:59
· 1 commit to main since this release

Two new sections in the detail panel, and a tab strip you can read at a glance.

Release — tags and the releases cut from them, side by side

A new tab pairs every tag in your repository with the release cut from it, one row per version. The states worth seeing are the ones where the two disagree: a tag nobody cut a release from, a release whose tag isn't in your clone, a tag that exists here and not on the remote.

Every tag now says where it actually is. git tag lists what's in your clone, which is not the same set as what's on origin — and that difference is invisible in most tools. A tag you made and never pushed looks identical to one everybody has; a tag a colleague pushed this morning doesn't appear at all. Each row is now marked on both, local only, or not fetched, and the actions follow: Push appears where there's something to push, Fetch where there's something to bring down, and neither is drawn where it would do nothing. One press fetches the whole backlog.

Select many, act on them, and see what happened to each. ⇧-click and ⌘-click to build a selection, then Push, Delete Locally or Delete on Remote. Ten pushes where three fail tell you which three and what Git said about each — "already exists" and "denied" are different problems. Stop ends a run, and what was never attempted is reported as exactly that rather than as a failure.

And it says what deleting a tag really does, before you confirm. Deleting a tag on GitHub doesn't delete its release: it turns it into a draft, which disappears from the public releases page — and pushing the tag back does not bring it back. The dialog tells you which case you're in, and when it can't know, it says that instead of guessing.

Long-lived repositories are handled: a filter over tag names and messages, and one list ordered newest-first whichever side supplies the date, so a tag pushed last week that you've never fetched sits at the top where it belongs.

Worktrees

A linked worktree is now a repository like any other: it appears in the browser, carries its own status, and the Branches tab gains a Worktrees section listing every worktree of the repository with the branch each one holds. Both Overviews count them.

A detail panel you can read

The tab strip was nine coloured pills competing for attention, with the selected one differing only in saturation, inside a box that sat apart from the panel it labelled. Now the unselected tabs are quiet and the selected one is filled with the colour its panel starts from, so tab and content read as one surface. The tabs are also in a more sensible order — what you're doing now, then this repository's refs, then what the forge says, then looking after the place.

Fixes

  • Issues and Pull Requests could show a stale answer. When two loads overlapped, the older one could land last and overwrite the newer. The newest load now wins in both tabs.
  • Italian called a linked worktree "alberi di lavoro". Corrected, along with a footnote's plural.
  • 189 user-facing strings were never in the translation catalogue, so they stayed English in every language while coverage read 100% — an absent string can't be reported missing. They're in, and translated.
  • Tags and releases in Italian, French, German and Spanish, including every confirmation dialog.

Verify this download

Compare the checksum of the file you downloaded:

shasum -a 256 FinderGit-0.31.0.dmg

It must print exactly:

7155e8742ad92e3985aa2f00bb56b69eb7672faf3aa747279ac8edce83c0fc0f

The DMG is also signed with an Apple Developer ID and notarized by Apple, which you can confirm without installing it:

spctl -a -vv -t open --context context:primary-signature FinderGit-0.31.0.dmg

That reports source=Notarized Developer ID for a genuine build.