<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Giovambattista Fazioli</title>
    <description>The latest articles on DEV Community by Giovambattista Fazioli (@undolog).</description>
    <link>https://dev.to/undolog</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2274629%2F3b560af3-80cf-412f-8373-cf54a218228e.jpeg</url>
      <title>DEV Community: Giovambattista Fazioli</title>
      <link>https://dev.to/undolog</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/undolog"/>
    <language>en</language>
    <item>
      <title>57 open-source projects, 775 stars, 20 hours a week: the honest economics</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Thu, 12 Nov 2026 13:28:18 +0000</pubDate>
      <link>https://dev.to/undolog/57-open-source-projects-775-stars-20-hours-a-week-the-honest-economics-1j69</link>
      <guid>https://dev.to/undolog/57-open-source-projects-775-stars-20-hours-a-week-the-honest-economics-1j69</guid>
      <description>&lt;p&gt;People see a GitHub profile with dozens of repos and assume one of two things. Either it’s a hobby that costs nothing, or there’s some money machine behind it they can’t see.&lt;/p&gt;

&lt;p&gt;Neither, at least for me. So I opened the spreadsheet. Everything below comes from my own &lt;a href="https://gfazioli.github.io/" rel="noopener noreferrer"&gt;project page&lt;/a&gt; and my repos, counted in mid-October 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  the numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;57 projects&lt;/strong&gt; across 9 categories: Mantine extensions, React components, macOS apps, CLI tools, WordPress plugins, templates, Raycast extensions, and a few arcade games.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;775 GitHub stars&lt;/strong&gt;, total.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;35 releases in the last 30 days.&lt;/strong&gt; Not a typo. That’s more than one a day.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;About 20 hours a week&lt;/strong&gt;, in the evenings after work and at weekends.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  where the stars actually are
&lt;/h2&gt;

&lt;p&gt;775 sounds like a lot spread over 57 projects. It isn’t spread at all.&lt;/p&gt;

&lt;p&gt;Four projects hold &lt;strong&gt;374 of them, 48%&lt;/strong&gt;: WP Bones (172), Mantine Split Pane (78), octoscope (69) and Mantine Onboarding Tour (55). The 26 Mantine components together have 411, more than half of everything.&lt;/p&gt;

&lt;p&gt;And here’s the part I find funny, in a slightly painful way. My three macOS apps, the ones I spend most of my time on right now, have &lt;strong&gt;35 stars combined&lt;/strong&gt;. FinderGit 18, Netfox 15, Lancetta 2.&lt;/p&gt;

&lt;p&gt;FinderGit alone went through 68 tagged versions between mid-April and early October. Lancetta shipped 32 releases in its first three weeks. That’s where my evenings go. 35 stars.&lt;/p&gt;

&lt;p&gt;Stars don’t measure work. They measure how many developers found the thing while browsing GitHub. A Mantine component is found by Mantine developers, who are on GitHub all day. A Mac app is found by Mac users, who mostly aren’t.&lt;/p&gt;

&lt;h2&gt;
  
  
  the money
&lt;/h2&gt;

&lt;p&gt;Let’s do the income side first, it’s quicker.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;GitHub Sponsors:&lt;/strong&gt; one recurring monthly sponsor. Thank you, you know who you are.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Donations:&lt;/strong&gt; nothing so far.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;The apps themselves:&lt;/strong&gt; free. All of them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now the costs.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;AI tools:&lt;/strong&gt; Claude Max on the 20x plan, plus ChatGPT Plus. This is the biggest line by far, and it’s what runs the whole studio: a set of agents, my “employees” as I like to call them, that help me maintain every project. Figuring out how to use them well is an ongoing experiment, and honestly half the fun.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Apple Developer Program:&lt;/strong&gt; the yearly fee. Without it you can’t sign and notarise a Mac app, and an unsigned app is an app nobody installs.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Domains:&lt;/strong&gt; one for each Mac app that has its own site, FinderGit, Netfox and Lancetta.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Hosting:&lt;/strong&gt; a Vercel plan. The project page itself is on GitHub Pages, so that part is free.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Writing:&lt;/strong&gt; including this. Right now Medium costs me more than it pays me.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Time:&lt;/strong&gt; those 20 hours a week. The one cost I never put a number on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can do the subtraction yourself. tbh I did it once and then stopped doing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  so why keep going?
&lt;/h2&gt;

&lt;p&gt;Because the subtraction is the wrong maths. What I get back doesn’t go in that column.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I build what I need first.&lt;/strong&gt; FinderGit exists because I was tired of tabbing between Finder and a Git client. Lancetta exists because I wanted a gauge while working with agents: hourly and daily token use at a glance, so I know when to slow down and when I can push. If nobody else ever used them, they’d still have paid for themselves in my own week. That someone else finds them useful too is the bonus, and it’s a good one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The community makes them better than I would alone.&lt;/strong&gt; The feedback, the bug reports, the “have you thought about…” from people I’ve never met. A lot of what FinderGit and Netfox do today started as a conversation on Product Hunt. Netfox can close the processes holding a port open because someone asked for it there. FinderGit’s sidebar got collapsible sections the same way. That’s the part I’d miss most.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It trains the muscle that matters most: not quitting.&lt;/strong&gt; Starting a side project is easy. Everyone has a folder of abandoned ones. The hard part is coming back to the same idea for the hundredth evening, when the fun part is long gone and what’s left is edge cases and release notes. Open source taught me to stay.&lt;/p&gt;

&lt;p&gt;And that’s how you get the thing I’m proudest of. Built piece by piece, step by step, in “spare time”, but with the same solidity as a commercial product. Signed, notarised, auto-updating, documented. Spare time doesn’t have to mean side-project quality.&lt;/p&gt;

&lt;p&gt;One thing I can say for sure: none of these projects would exist if I’d needed them to pay for themselves first.&lt;/p&gt;

&lt;h2&gt;
  
  
  what I’d tell someone starting today
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Build where your users already are.&lt;/strong&gt; My Mantine components get stars because Mantine developers live on GitHub. My Mac apps don’t, because Mac users don’t. If you want stars, build for developers. If you want users, go where users are, and accept that stars won’t follow.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;A release is not a launch.&lt;/strong&gt; 35 releases in a month got less attention than one article with a good title. Shipping is half the job. Telling people is the other half, and I’m still learning it.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Count it anyway.&lt;/strong&gt; I’d never added up my stars by project before writing this. The numbers changed what I think I’m building and for whom.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you maintain open source too, I’d love to hear your numbers. Especially if they look nothing like mine.&lt;/p&gt;

&lt;p&gt;And if any of my projects saved you some time, &lt;a href="https://github.com/sponsors/gfazioli" rel="noopener noreferrer"&gt;sponsoring on GitHub&lt;/a&gt; is the most direct way to keep them going. No pressure. A star helps too, apparently more than I thought.&lt;/p&gt;

&lt;p&gt;I’m Giovambattista Fazioli — I run &lt;a href="https://gfazioli.github.io/" rel="noopener noreferrer"&gt;Undolog&lt;/a&gt;, an open-source studio where I ship React components, Mantine extensions, macOS apps, WordPress plugins, and CLI tools. Been at it since 1983. You can find everything on &lt;a href="https://github.com/gfazioli" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://medium.com/@giovambattista.fazioli/57-open-source-projects-775-stars-20-hours-a-week-the-honest-economics-2b1f0edb3199?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>github</category>
      <category>opensource</category>
      <category>sideprojects</category>
    </item>
    <item>
      <title>FinderGit 0.44.0 — Cleaning: get your disk space back</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Sat, 03 Oct 2026 06:40:40 +0000</pubDate>
      <link>https://dev.to/undolog/findergit-0440-cleaning-get-your-disk-space-back-595g</link>
      <guid>https://dev.to/undolog/findergit-0440-cleaning-get-your-disk-space-back-595g</guid>
      <description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;FinderGit 0.44.0 adds a page I wanted for myself: &lt;strong&gt;Cleaning&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tens of gigabytes nobody wrote
&lt;/h2&gt;

&lt;p&gt;Work on a few JavaScript projects, an Xcode app and the odd Go tool, and your disk fills up with folders you never wrote: every project's node_modules, every Next.js .next, Xcode's DerivedData, the download caches of npm, Yarn, Homebrew and Go. They are all rebuildable, since the next install or build makes them again, and they add up. On my own Mac the first scan found about 30 GB.&lt;/p&gt;

&lt;p&gt;Cleaning sits under Account in the sidebar. The first time you open it, it scans your root folders, the caches in your home folder and every repository, and eight cards count up as the results arrive: node_modules, build output, Swift &amp;amp; Xcode, package caches, toolchains, Python, Git objects and a few other caches.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feoh7rp0wsoe35974jqb0.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feoh7rp0wsoe35974jqb0.webp" width="800" height="494"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Cleaning page on a set of demo projects: the two idle ones are ticked, the one changed today is left alone.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Only what you will not miss
&lt;/h2&gt;

&lt;p&gt;Open a card and you see each folder: its project, its size, when it last changed. FinderGit ticks for you only what is safe, not in use and, inside a project, untouched for a month. A folder a dev server or a terminal is working in, one you changed recently, or one that takes longer to get back carries a badge saying why, and the choice is yours.&lt;/p&gt;

&lt;p&gt;It is careful about what it calls rebuildable. Inside a repository, a folder is listed only when the repository's own .gitignore ignores it and it sits next to its project file, like a node_modules beside its package.json. Nothing Git tracks, no symbolic links, nothing inside .git. And each folder is checked again right before it goes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest numbers
&lt;/h2&gt;

&lt;p&gt;Each size is what deleting that folder alone gives back. Some package managers fill node_modules from a shared store, so part of what you see on disk is still held elsewhere, and Cleaning does not promise that as free space. The bar under the total shows your disk now and after cleaning.&lt;/p&gt;

&lt;p&gt;When you press Clean, it asks once and then works largest first, with a Stop. Folders are deleted rather than moved to the Trash: the space is the point.&lt;/p&gt;




&lt;p&gt;FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Website: findergit.app&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Download: &lt;a href="https://findergit.app/download" rel="noopener noreferrer"&gt;https://findergit.app/download&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/findergit-0-44-0-cleaning-get-your-disk-space-back-7yp17?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cleancode</category>
      <category>git</category>
      <category>github</category>
    </item>
    <item>
      <title>WP Bones 2.1.0 — the bones CLI, sturdier</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Fri, 25 Sep 2026 13:09:57 +0000</pubDate>
      <link>https://dev.to/undolog/wp-bones-210-the-bones-cli-sturdier-51e3</link>
      <guid>https://dev.to/undolog/wp-bones-210-the-bones-cli-sturdier-51e3</guid>
      <description>&lt;p&gt;The audit of the bones CLI had two halves. The first, 2.0.10, was about safety: a deploy that could delete the folder above your plugin. This is the second, and it is about the plumbing: the things bones quietly got wrong on an ordinary day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run it from anywhere
&lt;/h2&gt;

&lt;p&gt;bones used to work only from the plugin's own folder. Run &lt;code&gt;php my-plugin/bones&lt;/code&gt; from the folder above and it could not find the plugin's &lt;code&gt;namespace&lt;/code&gt; file, and stopped with a TypeError. Now it moves into the plugin before doing anything, and custom commands find WordPress from wherever you are. A relative &lt;code&gt;deploy&lt;/code&gt; path still means the folder you typed it in, and a plugin symlinked into &lt;code&gt;wp-content/plugins&lt;/code&gt; keeps working.&lt;/p&gt;

&lt;h2&gt;
  
  
  A rename that touches only what it must
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;rename&lt;/code&gt; rewrote every file of the plugin, changed or not. On the Internationalization boilerplate that was 187 files written, 99 of them identical to what they had been, and something worse: the compiled &lt;code&gt;.mo&lt;/code&gt; catalogues came out corrupted. A &lt;code&gt;.mo&lt;/code&gt; is a binary file with an offset table, and replacing &lt;code&gt;wp-kirk&lt;/code&gt; with a longer id shifts every string after it while the table stays put. Now only the files that change are written, and binary files are left alone.&lt;/p&gt;

&lt;p&gt;The same fix closes a nastier one. &lt;code&gt;rename --update&lt;/code&gt; runs after every &lt;code&gt;composer install&lt;/code&gt;, and it went through the whole rename again. In a renamed plugin with an &lt;code&gt;index.php&lt;/code&gt; in its root, it took that file for the main file of a pre-1.5 plugin and moved it over your real one. It now renames &lt;code&gt;vendor/&lt;/code&gt;, what Composer has just installed, and nothing else.&lt;/p&gt;

&lt;h2&gt;
  
  
  An update that can fail safely
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;php bones update&lt;/code&gt; deleted &lt;code&gt;vendor/wpbones/wpbones&lt;/code&gt; first, then ran &lt;code&gt;composer update&lt;/code&gt;. If Composer failed, with no network or a conflict, the plugin was left with no framework at all. Composer replaces the package by itself, so nothing is deleted first any more, and the command runs &lt;code&gt;composer update wpbones/wpbones --with-dependencies&lt;/code&gt;: the framework and what it needs, which is what "Update the Framework" in the help always promised.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F35kclxo6ewecr3p9y2pl.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F35kclxo6ewecr3p9y2pl.webp" width="799" height="433"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A format check that checks
&lt;/h2&gt;

&lt;p&gt;The &lt;code&gt;format:check&lt;/code&gt; script that &lt;code&gt;migrate:to-v2&lt;/code&gt; writes called &lt;code&gt;wp-scripts format --check&lt;/code&gt;. But &lt;code&gt;wp-scripts format&lt;/code&gt; drops &lt;code&gt;--check&lt;/code&gt; and always writes, so the "check" reformatted the plugin, compiled bundles included, and reported success. It is a real &lt;code&gt;prettier --check&lt;/code&gt; now, with a &lt;code&gt;.prettierignore&lt;/code&gt; that keeps &lt;code&gt;format&lt;/code&gt; away from &lt;code&gt;public/&lt;/code&gt; too. The boilerplates carry the new script, and their sources pass it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Widgets with their own identity
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;make:widget&lt;/code&gt; gave every widget of a plugin the same &lt;code&gt;id_base&lt;/code&gt;, and WordPress stores a widget's settings under its &lt;code&gt;id_base&lt;/code&gt;, so a second widget shared the first one's settings. The description sat under a misspelled key. Each widget now gets its id, name and description from its class name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Upgrading
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;composer update wpbones/wpbones&lt;/code&gt;. One behaviour to know: &lt;code&gt;php bones update&lt;/code&gt; now updates the framework and its dependencies, not every package of your plugin; for that, run &lt;code&gt;composer update&lt;/code&gt;. If your plugin was migrated before 2.1.0, its &lt;code&gt;format:check&lt;/code&gt; still points at &lt;code&gt;wp-scripts format --check&lt;/code&gt;, and the package.json page has the replacement. The 14 boilerplates and their Playground demos are already on 2.1.0, and the full notes are on GitHub.&lt;/p&gt;




&lt;p&gt;WP Bones is free and open source (LGPL-3.0), runs on PHP 8.1+, and installs with Composer.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Website: &lt;a href="https://wpbones.com" rel="noopener noreferrer"&gt;https://wpbones.com&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Docs: &lt;a href="https://wpbones.com/docs" rel="noopener noreferrer"&gt;https://wpbones.com/docs&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GitHub: &lt;a href="https://github.com/wpbones/WPBones" rel="noopener noreferrer"&gt;https://github.com/wpbones/WPBones&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/wp-bones-2-1-0-the-bones-cli-sturdier-2fxhz?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>framework</category>
      <category>laravel</category>
      <category>php</category>
      <category>plugins</category>
    </item>
    <item>
      <title>FinderGit 0.39.0 — Your own AI key, a whole changeset, and the file that made your repo heavy</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Mon, 21 Sep 2026 17:41:15 +0000</pubDate>
      <link>https://dev.to/undolog/findergit-0390-your-own-ai-key-a-whole-changeset-and-the-file-that-made-your-repo-heavy-8o6</link>
      <guid>https://dev.to/undolog/findergit-0390-your-own-ai-key-a-whole-changeset-and-the-file-that-made-your-repo-heavy-8o6</guid>
      <description>&lt;p&gt;FinderGit 0.39.0 is out, and it is the release where three long-standing &lt;em&gt;I wish it could…&lt;/em&gt; items finally landed.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Commit messages, on your own key if you want one&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;The free built-in mode stays exactly as it was — nothing to set up, nothing changes, and it is still the default. What is new sits beside it: you can bring your own provider and your own key.&lt;/p&gt;

&lt;p&gt;When you do, the key is kept in the macOS Keychain under an entry of its own, and the diff travels straight from your Mac to the service you picked. It does not pass through FinderGit at all. Point it at a server running on your own machine and nothing leaves the Mac in the first place.&lt;/p&gt;

&lt;p&gt;The key is checked before it is stored, so one that would be refused never gets saved. And when the check cannot reach a verdict — the service is down, the network is odd — the status line says the key was saved &lt;em&gt;unconfirmed&lt;/em&gt;, rather than claiming more than it knows.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Every change to Kaleidoscope, as one changeset&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;If you use Kaleidoscope, you could already send a single file’s diff. Now you can send the lot.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feyr5ig6lstlc2qqodzmd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feyr5ig6lstlc2qqodzmd.png" width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Diff All sits at the top of the file list on the Unstage tab. Staged and unstaged changes go over together, in one changeset.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Filter the tab to a directory and only that directory goes. Every comparison is pinned to the same commit, so a commit landing while the files are being prepared cannot mix two baselines into one review. And what cannot be sent — a directory, a submodule, a file git will not hand over — is listed underneath with the reason, instead of quietly missing from the changeset.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;The file that made your repository heavy&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;This is the one I have wanted for years. A repository that has become enormous can now name the object responsible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Largest objects in history&lt;/strong&gt; lists the twenty biggest, each with the path it was stored under — including files deleted from your working tree years ago, which is precisely why you could never find them by looking at your folder.&lt;/p&gt;

&lt;p&gt;The signal worth knowing about: an object sitting under a top-level folder your checkout does not have. That is the signature of a clone that swallowed a larger upstream.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fevbkmhpts5y5im9iwc33.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fevbkmhpts5y5im9iwc33.png" width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Maintenance tab separates a repository that is bloated from one that is merely big — a monorepo is legitimately gigabytes; a fork whose history swallowed one weighs the same and is a mistake.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Removing that history for good comes as a &lt;strong&gt;runbook, not a button&lt;/strong&gt;. &lt;em&gt;Show the rewrite runbook…&lt;/em&gt; hands you the exact commands for the paths you tick, to run against a fresh clone rather than your own folder. It opens with what it costs, before a single command: every commit from the first changed one onward gets a new identity, everyone else has to clone again, and open pull requests point at commits that no longer exist. FinderGit never runs them, deliberately — a rewrite cannot be undone and its blast radius reaches every clone.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;And the quieter half&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Every release the app carries is now readable in one window, under &lt;strong&gt;Help → Release Notes…&lt;/strong&gt;, with the ones you have not read still marked. If an update arrived while you were busy, you can still catch up instead of losing the panel you dismissed.&lt;/p&gt;

&lt;p&gt;Two windows can no longer act on the same repository at once, either. Each window used to keep its own idea of what was running, so a fetch in one and a pull in the other could reach the same folder together. A scheduled fetch now steps aside for you rather than refusing you.&lt;/p&gt;




&lt;p&gt;FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.&lt;/p&gt;

&lt;p&gt;FinderGit for macOS — Website: &lt;a href="https://findergit.app" rel="noopener noreferrer"&gt;https://findergit.app&lt;/a&gt; · Download: &lt;a href="https://findergit.app/download" rel="noopener noreferrer"&gt;https://findergit.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/findergit-0-39-0-your-own-ai-key-a-whole-changeset-and-the-file-that-made-your-repo-heavy-lz74x?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claude</category>
      <category>codex</category>
      <category>commitai</category>
      <category>git</category>
    </item>
    <item>
      <title>FinderGit 0.38.0 — branches, without the terminal</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Fri, 18 Sep 2026 15:06:58 +0000</pubDate>
      <link>https://dev.to/undolog/findergit-0380-branches-without-the-terminal-56oj</link>
      <guid>https://dev.to/undolog/findergit-0380-branches-without-the-terminal-56oj</guid>
      <description>&lt;p&gt;There is a particular moment this release is about. You are in the middle of something, you need a branch, and the app you are already looking at cannot make one — so you go and find a terminal, and by the time you come back you have lost the thread.&lt;/p&gt;

&lt;p&gt;FinderGit has listed branches and switched between them since 0.11.0. From 0.38.0 it does the rest: create, rename, merge, rebase, delete. &lt;strong&gt;New branch…&lt;/strong&gt; sits at the top of the branch dropdown, and it asks the two questions worth asking — where should it start, and do you want to be on it afterwards. Every row in the Branches tab carries the other four on a right-click.&lt;/p&gt;

&lt;p&gt;Three of the decisions in there are worth explaining, because they are the kind that look like omissions until you know why.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A remote row offers only Merge.&lt;/strong&gt; Renaming or deleting &lt;code&gt;origin/foo&lt;/code&gt; is not a local edit. It is a push to a remote that usually belongs to somebody else, which is a different thing with a different blast radius.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The rebase confirmation tells you something the screen would never suggest.&lt;/strong&gt; Git checks out the branch it is rebasing. You right-click a branch you are not standing on, and afterwards you are standing on it. That is Git's own behaviour rather than something the app adds, which is exactly why it should be said before you agree instead of discovered after.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Delete offers both ways out in the same dialog&lt;/strong&gt; — the ordinary one, and the forced one for a branch whose work is not merged anywhere. Showing you a refusal with no way forward is a dead end you would have to leave the app to escape.&lt;/p&gt;




&lt;p&gt;The second thing: if you have Kaleidoscope, a file's diff can go there. A button beside &lt;em&gt;Refresh Diff&lt;/em&gt; sends the committed version and your working copy across, in a tab named for the file.&lt;/p&gt;

&lt;p&gt;The reason to bother at all is binary files. They arrive intact — an image compared as an image, rather than as a wall of unprintable characters. A file you have just created shows an empty left side instead of an error. And if you do not have Kaleidoscope, the button is not drawn at all: a permanently greyed control advertising an app you have not bought tells you nothing you can act on.&lt;/p&gt;




&lt;p&gt;Then a set of smaller things, most of them about the app being straight with you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Two actions can no longer collide on the same repository.&lt;/strong&gt; Pressing Refresh in the middle of a fetch used to leave that fetch running with nothing watching it, and its result would land on a panel that had moved on. Now it is one at a time, and anything refused says so — a refresh across many repositories reports which ones it could not reach, rather than letting you assume it managed all of them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Counts agree with their numbers in Italian, French, German and Spanish.&lt;/strong&gt; Twenty-eight of them were being handed a single English sentence to cover both one and many, so every one read as a plural at one; in French and Spanish the adjective was wrong on top of that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The detail panel stops showing you the repository you just left.&lt;/strong&gt; Selecting the same path in a different project — a README, a lock file — kept the previous one's diff on screen, because the panel was recognising the path and not the repository it belongs to.&lt;/p&gt;




&lt;p&gt;FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.&lt;/p&gt;

&lt;p&gt;FinderGit for macOS — Website: &lt;a href="https://findergit.app" rel="noopener noreferrer"&gt;https://findergit.app&lt;/a&gt; · Download: &lt;a href="https://findergit.app/download" rel="noopener noreferrer"&gt;https://findergit.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/findergit-0-38-0-branches-without-the-terminal-8tq3y?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>git</category>
      <category>github</category>
      <category>macos</category>
    </item>
    <item>
      <title>Netfox 0.23.0 — the devices that never speak</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Thu, 17 Sep 2026 13:09:16 +0000</pubDate>
      <link>https://dev.to/undolog/netfox-0230-the-devices-that-never-speak-3o7o</link>
      <guid>https://dev.to/undolog/netfox-0230-the-devices-that-never-speak-3o7o</guid>
      <description>&lt;p&gt;There is a particular kind of thing on your network that Netfox could never show you, and it was not a gap in the feature list. It was structural.&lt;/p&gt;

&lt;p&gt;Netfox found devices by &lt;strong&gt;listening&lt;/strong&gt;. Some things announce themselves; others give themselves away by exchanging a packet with something. Between the two, most of a home network turns up. But a device that is switched on, quiet, and has never had a reason to talk to your Mac produces neither signal — so it was not merely hard to find, it was unreachable by construction. A printer asleep. A camera that only ever phones its own cloud. Something you set up months ago and stopped thinking about.&lt;/p&gt;

&lt;h2&gt;
  
  
  Now it can ask
&lt;/h2&gt;

&lt;p&gt;Give Netfox a range of addresses and it sends one small question to each. Whatever answers turns up as an ordinary device — its identity, its history, its alerts, all of it — because the sweep does not create a parallel list, it feeds the one you already have.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0zwicfbb9f17rul5cwmb.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0zwicfbb9f17rul5cwmb.webp" alt="The Devices list with Demo Mode on. The new range control sits in the toolbar, right of the Online/Offline filter; a sweep adds to this list rather than opening one of its own." width="800" height="524"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It stays inside your own subnet, needs no password and installs nothing. A range that reaches outside is refused rather than trimmed to fit, because a trimmed range asks about a different set of addresses than the one you typed, and nothing on screen would tell you.&lt;/p&gt;

&lt;h2&gt;
  
  
  The range is also a filter, and that is the important half
&lt;/h2&gt;

&lt;p&gt;Set it to two addresses and the list shows those two devices. Nothing else.&lt;/p&gt;

&lt;p&gt;This started as a way to bound how long a sweep takes and turned out to be the thing that makes the feature trustworthy: &lt;strong&gt;you can see what it found.&lt;/strong&gt; Set a narrow range, look, and know. While a range is active the control that set it says so and offers to clear it, and the footer carries both numbers — &lt;em&gt;2 in range · 33 on the network&lt;/em&gt; — because a filter you have forgotten looks exactly like a network that has lost thirty devices, and nothing else on screen would disagree with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is holding that port on your own Mac
&lt;/h2&gt;

&lt;p&gt;Open the Ports tab for your own machine and each row now names what holds the port: the process, the user it runs as, its ID. A click deeper says how it is managed, and whether closing it can be undone.&lt;/p&gt;

&lt;p&gt;That last one is worth dwelling on, because it is the difference between a decision and a one-way door. Netfox asks your Mac rather than guessing, and the honest answer is usually no: most services, once you stop them, stay stopped until something asks for them again. On the machine this was measured on, &lt;strong&gt;only 2 of 36 running services were set to restart themselves.&lt;/strong&gt; A tool that told you "it'll come back" would have been wrong about the other 34.&lt;/p&gt;

&lt;h2&gt;
  
  
  Smaller things you will notice
&lt;/h2&gt;

&lt;p&gt;Inspecting a port that has closed since the last scan no longer keeps you waiting. A refusal is an answer, and it arrives in about a millisecond — it was being read as a silence, so every inspection sat out its full timeout behind a spinner, on something you had just clicked.&lt;/p&gt;

&lt;p&gt;And two things on the Overview stopped moving about: the summary cards now reach the right edge of the window instead of leaving an empty column beside them, and the line under the Wi-Fi figures keeps one height whether the rate is holding, has just renegotiated, or has not been measured twice yet. A fast radio drifting between 864 Mb/s and 1.4 Gb/s was resizing the whole card every couple of seconds.&lt;/p&gt;




&lt;p&gt;Netfox is free, a universal binary (Apple Silicon + Intel), runs on macOS 15.6+, and is signed and notarized.&lt;/p&gt;

&lt;p&gt;Netfox for macOS — Website: &lt;a href="https://netfox.app" rel="noopener noreferrer"&gt;https://netfox.app&lt;/a&gt; · Download: &lt;a href="https://netfox.app/download" rel="noopener noreferrer"&gt;https://netfox.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/netfox-0-23-0-the-devices-that-never-speak-c749m?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>macos</category>
      <category>network</category>
      <category>security</category>
      <category>tooling</category>
    </item>
    <item>
      <title>octoscope 0.35.0 — your activity, in the right order</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Wed, 16 Sep 2026 08:03:22 +0000</pubDate>
      <link>https://dev.to/undolog/octoscope-0350-your-activity-in-the-right-order-47jf</link>
      <guid>https://dev.to/undolog/octoscope-0350-your-activity-in-the-right-order-47jf</guid>
      <description>&lt;h2&gt;
  
  
  Your activity, now in --json and --plain
&lt;/h2&gt;

&lt;p&gt;octoscope has two halves. There is the dashboard you sit in front of, and there is the quiet half — &lt;code&gt;--json&lt;/code&gt; and &lt;code&gt;--plain&lt;/code&gt; — which exists so you can pipe octoscope into something else: a status bar, a cron job, a script that nudges you when something needs attention.&lt;/p&gt;

&lt;p&gt;Until now that quiet half could tell you everything about your repositories and nothing about &lt;em&gt;you&lt;/em&gt;. The Activity tab was screen-only.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;--activity&lt;/code&gt; changes that. Same events, same fields, in both output formats.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;octoscope --json --activity
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One small decision that will matter if you build on it: when you do not ask for the feed, the &lt;code&gt;recent_activity&lt;/code&gt; key is &lt;strong&gt;absent&lt;/strong&gt;, not empty. An empty list would be a claim — "we looked, there was nothing" — and that claim would be false. A missing key lets your script tell &lt;em&gt;did not fetch&lt;/em&gt; from &lt;em&gt;nothing happened&lt;/em&gt;. And when you do ask and the fetch fails, that is an error, not silence.&lt;/p&gt;

&lt;h2&gt;
  
  
  The feed was never in chronological order
&lt;/h2&gt;

&lt;p&gt;Here is the part nobody went looking for.&lt;/p&gt;

&lt;p&gt;While wiring the feed into the reports, we checked the order. It was wrong. Not occasionally — &lt;strong&gt;27 of 99&lt;/strong&gt; adjacent events came back out of sequence, then 28 in the next feed, then 25 in the one after that.&lt;/p&gt;

&lt;p&gt;The events endpoint is not documented as returning a sorted feed, and it does not. octoscope had been trusting the order it was handed, which means the Activity tab has been showing you an &lt;em&gt;almost&lt;/em&gt; sorted list this whole time. That is worse than an obviously unsorted one, because it reads as correct.&lt;/p&gt;

&lt;p&gt;It is sorted now, at the point where events are parsed — so the tab and the reports are fixed by the same change. If you have ever glanced at Activity and thought "hang on, didn't I do that after the other thing?", you were right.&lt;/p&gt;

&lt;h2&gt;
  
  
  The scan reads the repository's own settings
&lt;/h2&gt;

&lt;p&gt;The supply-chain scan watches for workflows triggered by things outsiders can send: issues, discussions, discussion comments, forks. It now checks whether the repository actually &lt;em&gt;allows&lt;/em&gt; those things.&lt;/p&gt;

&lt;p&gt;A workflow reacting to discussions on a repository with discussions turned off is not an exposure. Neither is &lt;code&gt;issues&lt;/code&gt; on a repository only your collaborators can open one on.&lt;/p&gt;

&lt;p&gt;This moves scores in &lt;strong&gt;both&lt;/strong&gt; directions, which is worth saying plainly rather than selling as an improvement: you will see fewer findings where a repository's settings make a trigger unreachable, and &lt;strong&gt;more&lt;/strong&gt; on private and internal repositories, where the axis used to stay quiet — which is exactly the case where someone with read access is the supplier worth worrying about.&lt;/p&gt;

&lt;h2&gt;
  
  
  Also in this release
&lt;/h2&gt;

&lt;p&gt;The What's new tab had a bug where a long title ran off the edge of the pane instead of wrapping. Fixing the renderer also repairs the entries that shipped back in 0.34.1, not just this release's.&lt;/p&gt;

&lt;p&gt;And on macOS, a release is now verified &lt;em&gt;before&lt;/em&gt; it becomes downloadable rather than after: the signature, the hardened runtime and Apple's notarization are all checked against the files that were actually uploaded, and only then does the release go public.&lt;/p&gt;

&lt;h2&gt;
  
  
  Upgrade
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew upgrade gfazioli/tap/octoscope
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;Site: &lt;a href="https://gfazioli.github.io/octoscope" rel="noopener noreferrer"&gt;https://gfazioli.github.io/octoscope&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Newsletter: &lt;a href="https://octoscope.substack.com" rel="noopener noreferrer"&gt;https://octoscope.substack.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Mastodon: &lt;a href="https://hachyderm.io/@undolog" rel="noopener noreferrer"&gt;https://hachyderm.io/@undolog&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/octoscope-0-35-0-your-activity-in-the-right-order-kqwwc?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>bubbletea</category>
      <category>cli</category>
      <category>git</category>
      <category>github</category>
    </item>
    <item>
      <title>The two gaps from last time are closed</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Mon, 14 Sep 2026 13:56:57 +0000</pubDate>
      <link>https://dev.to/undolog/the-two-gaps-from-last-time-are-closed-a0p</link>
      <guid>https://dev.to/undolog/the-two-gaps-from-last-time-are-closed-a0p</guid>
      <description>&lt;h2&gt;
  
  
  🪟 Window 3.2.0 — the edges of a gesture
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;Window&lt;/code&gt; now has the full set of six lifecycle callbacks, matching core's &lt;code&gt;FloatingWindow&lt;/code&gt;: &lt;code&gt;onDragStart&lt;/code&gt;, &lt;code&gt;onDragEnd&lt;/code&gt;, &lt;code&gt;onResizeStart&lt;/code&gt; and &lt;code&gt;onResizeEnd&lt;/code&gt; alongside the two change callbacks it already had.&lt;/p&gt;

&lt;p&gt;The two &lt;em&gt;change&lt;/em&gt; callbacks fire on every frame of a gesture, so anything you wanted to do &lt;strong&gt;once&lt;/strong&gt; — persist a layout, pause an expensive child, show a snap guide, record a single undo entry — meant debouncing by hand and guessing when the user had stopped. Fully additive: four optional props, no default changed. A mousedown on an interactive child or a &lt;code&gt;data-no-window-drag&lt;/code&gt; region still does not open a drag, so no start event fires there, and a resize never emits drag callbacks. &lt;a href="https://github.com/gfazioli/mantine-window/issues/47" rel="noopener noreferrer"&gt;Closes #47&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ferw0q2gtpnnp8yoqp7xz.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ferw0q2gtpnnp8yoqp7xz.webp" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📚 &lt;a href="https://gfazioli.github.io/mantine-window/" rel="noopener noreferrer"&gt;Docs and live demo&lt;/a&gt; · 📦 &lt;a href="https://www.npmjs.com/package/@gfazioli/mantine-window" rel="noopener noreferrer"&gt;npm&lt;/a&gt; · 🏷️ &lt;a href="https://github.com/gfazioli/mantine-window/releases/tag/3.2.0" rel="noopener noreferrer"&gt;Release 3.2.0&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  📋 ListViewTable 4.1.10 — bulk actions, with no new API
&lt;/h2&gt;

&lt;p&gt;Mantine 9.6's &lt;code&gt;ActionBar&lt;/code&gt; is built to be driven by a table selection, and &lt;code&gt;ListViewTable&lt;/code&gt; already had &lt;code&gt;selectionMode&lt;/code&gt;, &lt;code&gt;selectedRows&lt;/code&gt; and &lt;code&gt;onSelectionChange&lt;/code&gt;. There is now a demo showing the two composing: &lt;code&gt;opened&lt;/code&gt; follows the length of the selection, the buttons act on the records handed to &lt;code&gt;onSelectionChange&lt;/code&gt;, and &lt;code&gt;ActionBar.CloseButton&lt;/code&gt; clears it through &lt;code&gt;onClose&lt;/code&gt;. Nothing was added to the library — the capability was there, the demonstration was not. Closes #41.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft67vhndxdvyti0r2qs4r.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft67vhndxdvyti0r2qs4r.webp" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📚 &lt;a href="https://gfazioli.github.io/mantine-list-view-table/" rel="noopener noreferrer"&gt;Docs and live demo&lt;/a&gt; · 📦 &lt;a href="https://www.npmjs.com/package/@gfazioli/mantine-list-view-table" rel="noopener noreferrer"&gt;npm&lt;/a&gt; · 🏷️ &lt;a href="https://github.com/gfazioli/mantine-list-view-table/releases/tag/4.1.10" rel="noopener noreferrer"&gt;Release 4.1.10&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  ✨ BorderAnimate 3.0.2 — where the border actually goes
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;BorderAnimate&lt;/code&gt; draws its border against its own root. The Input Fields demo wrapped a whole &lt;code&gt;TextInput&lt;/code&gt; — an &lt;code&gt;Input.Wrapper&lt;/code&gt;: label, description, control and error in one box — so the animated border enclosed the label and a radius set to match the input traced a much taller box. The rule, now in the docs: &lt;code&gt;Input.Wrapper&lt;/code&gt; holds the label, &lt;code&gt;BorderAnimate&lt;/code&gt; holds only the &lt;code&gt;Input&lt;/code&gt;. The same shape had leaked into the Triggers demo, where the &lt;code&gt;focus-within&lt;/code&gt; card was a &lt;code&gt;TextInput&lt;/code&gt; while its siblings were &lt;code&gt;Paper&lt;/code&gt; + &lt;code&gt;Text&lt;/code&gt;; all three are now built the same way. Closes &lt;a href="https://github.com/gfazioli/mantine-border-animate/issues/33" rel="noopener noreferrer"&gt;#33&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7evdrovvxzcg8f1nnnnj.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7evdrovvxzcg8f1nnnnj.webp" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📚 &lt;a href="https://gfazioli.github.io/mantine-border-animate/" rel="noopener noreferrer"&gt;Docs and live demo&lt;/a&gt; · 📦 &lt;a href="https://www.npmjs.com/package/@gfazioli/mantine-border-animate" rel="noopener noreferrer"&gt;npm&lt;/a&gt; · 🏷️ &lt;a href="https://github.com/gfazioli/mantine-border-animate/releases/tag/3.0.2" rel="noopener noreferrer"&gt;Release 3.0.2&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🃏 Flip 4.0.14 — the picker that was unstyled for months
&lt;/h2&gt;

&lt;p&gt;The credit-card demo's &lt;code&gt;MonthPickerInput&lt;/code&gt; rendered fine and came up bare: &lt;code&gt;@mantine/dates&lt;/code&gt; was a declared dependency but its stylesheet was never imported in the docs bootstrap. Nothing fails when that import is missing, which is why it survived.&lt;/p&gt;

&lt;p&gt;📚 &lt;a href="https://gfazioli.github.io/mantine-flip/" rel="noopener noreferrer"&gt;Docs and live demo&lt;/a&gt; · 📦 &lt;a href="https://www.npmjs.com/package/@gfazioli/mantine-flip" rel="noopener noreferrer"&gt;npm&lt;/a&gt; · 🏷️ &lt;a href="https://github.com/gfazioli/mantine-flip/releases/tag/4.0.14" rel="noopener noreferrer"&gt;Release 4.0.14&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🔧 Mantine 9.6.1, everywhere
&lt;/h2&gt;

&lt;p&gt;Mantine 9.6.1 and React 19.3 across every component, both starter templates and the Hub, with Next 16.3.5 and a round of tooling updates. Peer ranges unchanged (&lt;code&gt;&amp;gt;=9.0.0&lt;/code&gt;). Templates: &lt;a href="https://github.com/gfazioli/next-app-nextra-template/releases/tag/v6.0.16" rel="noopener noreferrer"&gt;Nextra starter 6.0.16&lt;/a&gt;, &lt;a href="https://github.com/gfazioli/next-app-fumadocs-template/releases/tag/v1.0.10" rel="noopener noreferrer"&gt;Fumadocs starter 1.0.10&lt;/a&gt;, Hub 1.0.15.&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://mantine-extensions.vercel.app/" rel="noopener noreferrer"&gt;Browse every component on the Hub&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🛠️ Infrastructure
&lt;/h2&gt;

&lt;p&gt;Every GitHub Action is pinned to a commit SHA with the version as a trailing comment, with Dependabot opening a grouped PR when an action ships a release. The bot configuration is now byte-identical across every component repository, and a repository that had been running a second update bot in parallel was brought back in line — two bots proposing overlapping updates produced pull requests that were obsolete by the time anyone read them.&lt;/p&gt;

&lt;h2&gt;
  
  
  💡 Pro Tip
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;A Mantine package used in your app needs its stylesheet imported, and nothing fails if it isn't.&lt;/strong&gt; Declaring &lt;code&gt;@mantine/dates&lt;/code&gt; and rendering a &lt;code&gt;MonthPickerInput&lt;/code&gt; gets you a working, interactive, &lt;em&gt;unstyled&lt;/em&gt; component — no error, no warning, no failed build.&lt;/p&gt;

&lt;p&gt;The part worth keeping is how to check it rather than squinting at a screenshot. Mantine's built CSS ships &lt;strong&gt;hashed&lt;/strong&gt; class names (&lt;code&gt;.m_14c23465&lt;/code&gt;), not the readable &lt;code&gt;mantine-MonthPicker-*&lt;/code&gt; seen in devtools, so grepping loaded stylesheets for &lt;code&gt;"PickerControl"&lt;/code&gt; finds nothing whether or not the import is there — it looks like the bug either way. Pick a hashed selector present in that package's &lt;code&gt;styles.css&lt;/code&gt; and in no other, then count matching loaded rules: it went from &lt;strong&gt;0 to 10&lt;/strong&gt; with one import line. A number you can read beats an impression of "looks about right".&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/the-two-gaps-from-last-time-are-closed-ttxsq?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>FinderGit 0.31.0 — Your tags and your releases, side by side</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Thu, 10 Sep 2026 07:18:38 +0000</pubDate>
      <link>https://dev.to/undolog/findergit-0310-your-tags-and-your-releases-side-by-side-1gof</link>
      <guid>https://dev.to/undolog/findergit-0310-your-tags-and-your-releases-side-by-side-1gof</guid>
      <description>&lt;p&gt;There’s a small lie every Git tool tells you, and it’s so quiet that most of us stopped noticing.&lt;/p&gt;

&lt;p&gt;When you ask for your tags, you get the ones in &lt;em&gt;your&lt;/em&gt; clone. Not the ones on the remote — the ones on your disk. A tag you cut this morning and never pushed looks exactly like one everybody on the team has had for a year. A tag a colleague pushed an hour ago simply isn’t there, and nothing tells you to go looking. The list is honest about what it contains and silent about what it means, and the difference between those two things is where releases go wrong.&lt;/p&gt;

&lt;p&gt;FinderGit 0.31.0 puts that difference on screen.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Every tag now says where it is&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foof656srwo77cky0cuxj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foof656srwo77cky0cuxj.png" title="The new Release tab: tags on the left, the releases cut from them on the right, and a presence badge on every row." alt="The new Release tab: tags on the left, the releases cut from them on the right, and a presence badge on every row." width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The new Release tab: tags on the left, the releases cut from them on the right, and a presence badge on every row.&lt;/p&gt;

&lt;p&gt;A new tab in the detail panel pairs every tag in your repository with the release cut from it, one row per version, the two columns side by side. The rows worth looking at are the ones where the two halves disagree: a tag nobody ever cut a release from, a release whose tag isn’t in your clone, a tag that exists here and nowhere else.&lt;/p&gt;

&lt;p&gt;Each row is marked &lt;strong&gt;on both&lt;/strong&gt;, &lt;strong&gt;local only&lt;/strong&gt;, or &lt;strong&gt;not fetched&lt;/strong&gt; — and the buttons follow from that rather than being drawn regardless. Push appears where there is something to push. Fetch appears where there is something to bring down. Neither is drawn where pressing it would do nothing at all. One press brings down the whole backlog.&lt;/p&gt;

&lt;p&gt;Select several rows — ⇧-click, ⌘-click, the way you’d expect — and act on all of them: push, delete locally, delete on the remote. Ten pushes where three fail will tell you &lt;em&gt;which three&lt;/em&gt;, and what Git actually said about each one, because “already exists” and “denied” are entirely different problems with entirely different fixes. There’s a Stop, and when you use it, the rows that were never attempted are reported as exactly that instead of being quietly counted as failures.&lt;/p&gt;

&lt;p&gt;And when you delete a tag, the dialog tells you what that really costs — which turned out to be worth measuring rather than assuming. Deleting a tag on GitHub doesn’t delete its release: it turns the release into a draft, which vanishes from your public releases page. Pushing the tag back does &lt;strong&gt;not&lt;/strong&gt; bring it back. The confirmation now tells you which case you’re in, and on the rare occasion it can’t know, it says so rather than guessing.&lt;/p&gt;

&lt;p&gt;Long-lived repositories were kept in mind: there’s a filter across tag names and messages, and the list is ordered newest-first whichever side supplies the date — so a tag a colleague pushed last week that you’ve never fetched sits at the top, where it belongs, instead of alphabetically buried.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Worktrees are repositories now&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqj17nxdkw0e1c0hwpujo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqj17nxdkw0e1c0hwpujo.png" title="The Branches tab, with the new Worktrees section at the bottom — here with none linked, explaining what one is for." alt="The Branches tab, with the new Worktrees section at the bottom — here with none linked, explaining what one is for." width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The Branches tab, with the new Worktrees section at the bottom — here with none linked, explaining what one is for.&lt;/p&gt;

&lt;p&gt;If you use linked worktrees to keep a second branch checked out in its own folder, FinderGit now treats each one as a repository like any other: it shows up in the browser, carries its own status, and both Overviews count it. The Branches tab has gained a Worktrees section listing every worktree of the repository and the branch each one is holding.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;A detail panel you can actually read&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fns15es3laj8ltkazkbk9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fns15es3laj8ltkazkbk9.png" title="The detail panel's tab strip: the selected tab is filled with the colour its panel starts from, so the two read as one surface." alt="The detail panel's tab strip: the selected tab is filled with the colour its panel starts from, so the two read as one surface." width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The detail panel’s tab strip: the selected tab is filled with the colour its panel starts from, so the two read as one surface.&lt;/p&gt;

&lt;p&gt;The tab strip had become nine coloured pills all competing for your attention, with the selected one differing from the rest only in saturation — inside a box that visibly sat apart from the panel it was labelling. At a glance you couldn’t tell what you were looking at.&lt;/p&gt;

&lt;p&gt;Now the unselected tabs are quiet, and the selected one is filled with the colour its panel starts from, so the tab and its content read as a single surface. The order changed too, into something that follows how you actually work: what you’re doing right now, then this repository’s refs, then what the forge has to say, then looking after the place.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Fixes&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Issues and Pull Requests could show you a stale answer.&lt;/strong&gt; When two loads overlapped, the older one could land last and overwrite the newer. The newest load now wins, in both tabs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A large gap in the translations closed.&lt;/strong&gt; A count of user-facing strings — 189 of them — had never made it into the translation catalogue at all, so they stayed in English in every language while the coverage report happily read 100%. It was right, on its own terms: a string that never became a key can’t be reported as missing. They’re in now, and translated. Tags and releases are fully translated too, including every confirmation dialog, and the Italian word for a linked worktree has been corrected.&lt;/p&gt;




&lt;p&gt;FinderGit is free, a universal binary (Apple Silicon + Intel), runs on macOS 15+, and is signed and notarized.&lt;/p&gt;

&lt;p&gt;FinderGit for macOS — Website: &lt;a href="https://findergit.app" rel="noopener noreferrer"&gt;https://findergit.app&lt;/a&gt; · Download: &lt;a href="https://findergit.app/download" rel="noopener noreferrer"&gt;https://findergit.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Published via &lt;a href="https://zyvop.com/findergit-0-31-0-your-tags-and-your-releases-side-by-side-1dwxk?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt; — Write once in Markdown, auto-backup to GitHub, and syndicate to Dev.to, Medium &amp;amp; Hashnode in 1 click.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>swift</category>
      <category>macos</category>
      <category>git</category>
      <category>github</category>
    </item>
    <item>
      <title>The test that could only pass, and the warning that admitted it didn't know</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Wed, 09 Sep 2026 08:21:00 +0000</pubDate>
      <link>https://dev.to/undolog/the-test-that-could-only-pass-and-the-warning-that-admitted-it-didnt-know-246p</link>
      <guid>https://dev.to/undolog/the-test-that-could-only-pass-and-the-warning-that-admitted-it-didnt-know-246p</guid>
      <description>&lt;p&gt;&lt;em&gt;FinderGit is a Git-aware file browser for macOS: every repository you own in one window, with status, branches, issues and pull requests inline. This story comes from building a new tab in it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzf5n7mr9jctdx67b2kai.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzf5n7mr9jctdx67b2kai.webp" alt="Findergit" width="800" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I shipped two sentences last week that looked like verification and were not. One was a test. One was a warning in a dialog. They failed in the same way, and finding the second one only happened because the first one taught me what to look for.&lt;/p&gt;

&lt;h2&gt;
  
  
  One: a test that was green for the wrong reason
&lt;/h2&gt;

&lt;p&gt;I was adding bulk actions to a tag list — select ten tags, push them, delete them. Bulk operations need a Stop button, and a stopped run has to report the difference between &lt;em&gt;this failed&lt;/em&gt; and &lt;em&gt;we never got to it&lt;/em&gt;. A red mark next to a tag because you pressed Stop reads as "the app broke", which is both wrong and the opposite of reassuring.&lt;/p&gt;

&lt;p&gt;So the outcome type has three cases, not two:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="k"&gt;struct&lt;/span&gt; &lt;span class="nc"&gt;BulkResult&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;enum&lt;/span&gt; &lt;span class="nc"&gt;Kind&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt; &lt;span class="n"&gt;success&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;failure&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;cancelled&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Kind&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And here is the test I wrote for it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="nd"&gt;@Test&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"A stopped run reports the rest as not attempted, never as failed"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;func&lt;/span&gt; &lt;span class="nf"&gt;cancellationIsNotFailure&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="k"&gt;throws&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;repo&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="nc"&gt;Fixture&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tags&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"c1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c2"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c3"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c4"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;store&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;RepoTagStore&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;task&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Task&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;runBulk&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;deleteLocal&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"c1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c2"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c3"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c4"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;repo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;cancel&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;results&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;

    &lt;span class="cp"&gt;#expect(results.count == 4)&lt;/span&gt;
    &lt;span class="cp"&gt;#expect(results.allSatisfy { $0.kind != .failure })&lt;/span&gt;
    &lt;span class="cp"&gt;#expect(results.contains { $0.kind == .cancelled })&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Green. Every assertion passes. And it proves nothing at all.&lt;/p&gt;

&lt;p&gt;The cancel lands before the loop reaches its first item, so &lt;code&gt;runBulk&lt;/code&gt; sees &lt;code&gt;Task.isCancelled&lt;/code&gt; on iteration zero and marks &lt;strong&gt;all four&lt;/strong&gt; &lt;code&gt;.cancelled&lt;/code&gt;. &lt;code&gt;allSatisfy { $0.kind != .failure }&lt;/code&gt; is trivially true when nothing ran. &lt;code&gt;contains { $0.kind == .cancelled }&lt;/code&gt; is trivially true when everything is cancelled. The mixed outcome — some done, then Stop, then the rest — is the only case a user ever produces, and the test never touched it.&lt;/p&gt;

&lt;p&gt;The rewrite cancels from &lt;em&gt;inside&lt;/em&gt; the progress callback, after two items have gone through:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="kd"&gt;final&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;Box&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nd"&gt;@unchecked&lt;/span&gt; &lt;span class="nc"&gt;Sendable&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="kd"&gt;var&lt;/span&gt; &lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Task&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nc"&gt;BulkResult&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Never&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;?&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;box&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Box&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;box&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;task&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Task&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;runBulk&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;deleteLocal&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"c1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c2"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c3"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"c4"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;repo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;done&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;done&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;box&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;cancel&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;results&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;box&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;task&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;

&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;done&lt;/span&gt;    &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;filter&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nv"&gt;$0&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;kind&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;success&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;skipped&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;filter&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nv"&gt;$0&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;kind&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cancelled&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="cp"&gt;#expect(!done.isEmpty,    "the work done before the stop must be kept")&lt;/span&gt;
&lt;span class="cp"&gt;#expect(!skipped.isEmpty, "and the rest reported as not attempted")&lt;/span&gt;
&lt;span class="cp"&gt;#expect(done.count + skipped.count == 4)&lt;/span&gt;

&lt;span class="c1"&gt;// And the repository agrees: exactly the ones reported done are gone.&lt;/span&gt;
&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;remaining&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="n"&gt;repo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;tagNames&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;done&lt;/span&gt;    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="cp"&gt;#expect(!remaining.contains(r.name)) }&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;skipped&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="cp"&gt;#expect(remaining.contains(r.name)) }&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It went red immediately:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;Expectation failed: &lt;span class="o"&gt;(&lt;/span&gt;done.count + skipped.count → 3&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; 4
Expectation failed: results.allSatisfy &lt;span class="o"&gt;{&lt;/span&gt; &lt;span class="nv"&gt;$0&lt;/span&gt;.kind != .failure &lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three of four accounted for. One result was &lt;code&gt;.failure&lt;/code&gt; — and there was no failure. It was the tag &lt;strong&gt;in flight&lt;/strong&gt; at the moment Stop was pressed: the child process gets signalled, &lt;code&gt;git tag -d&lt;/code&gt; dies, and my code read that as the tag failing to delete.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix was a rule the codebase had already written down
&lt;/h2&gt;

&lt;p&gt;Here is what my bulk runner did:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;failure&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;String&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;runRaw&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;
    &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;client&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;deleteTag&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;repoURL&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;BulkResult&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;failure&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="kc"&gt;nil&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;success&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;failure&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;   &lt;span class="c1"&gt;// ← the error's TYPE is gone&lt;/span&gt;
    &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;failure&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;runRaw&lt;/code&gt; caught everything and turned it into a &lt;code&gt;String?&lt;/code&gt;. Convenient, and it throws away the one piece of information that separates a stop from a breakage.&lt;/p&gt;

&lt;p&gt;The obvious repair is to ask the task: &lt;em&gt;were we cancelled? then call it cancelled.&lt;/em&gt; That is exactly wrong, and this project had already learned why — in a comment I had read more than once, in a different file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="c1"&gt;/// Reads the **error only**, and that took two goes to get right.&lt;/span&gt;
&lt;span class="c1"&gt;///&lt;/span&gt;
&lt;span class="c1"&gt;/// [...] consulting the caller's task handle worked for the common case and&lt;/span&gt;
&lt;span class="c1"&gt;/// quietly broke a rarer one: a genuine failure — a rejected credential, an&lt;/span&gt;
&lt;span class="c1"&gt;/// unreachable host — that raced with a late stop was reported as the stop, so&lt;/span&gt;
&lt;span class="c1"&gt;/// the user pressed a button and lost the reason their push had actually failed.&lt;/span&gt;
&lt;span class="c1"&gt;///&lt;/span&gt;
&lt;span class="c1"&gt;/// So the information now comes from where it is known: `awaitExit` throws&lt;/span&gt;
&lt;span class="c1"&gt;/// `CancellationError` when *it* signalled the child. An error that isn't one is&lt;/span&gt;
&lt;span class="c1"&gt;/// a real failure, whether or not a stop arrived while it was being thrown.&lt;/span&gt;
&lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="k"&gt;func&lt;/span&gt; &lt;span class="nf"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;error&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Error&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&amp;gt;&lt;/span&gt; &lt;span class="nc"&gt;Kind&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;error&lt;/span&gt; &lt;span class="k"&gt;is&lt;/span&gt; &lt;span class="nc"&gt;CancellationError&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cancelled&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;failure&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The error already carries the truth. So the runner rethrows instead of stringifying:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="k"&gt;do&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;try&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;perform&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;action&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;repoURL&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;BulkResult&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;success&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;nil&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;catch&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;error&lt;/span&gt; &lt;span class="k"&gt;is&lt;/span&gt; &lt;span class="nc"&gt;CancellationError&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;cancelled&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
        &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;BulkResult&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;cancelled&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;nil&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;BulkResult&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;failure&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;message&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;for&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;error&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Green, and green for the right reason this time.  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The thing worth carrying:&lt;/strong&gt; a cancellation test that cancels before the work starts is the equivalent of testing a parser on an empty string. Ask what the failing case would need to look like, then check your test actually builds it. If cancelling at a different moment changes the result, the moment is part of the test.  &lt;/p&gt;

&lt;h2&gt;
  
  
  Two: a warning that admitted it didn't know
&lt;/h2&gt;

&lt;p&gt;Same feature, different sentence. Deleting a tag on the remote is the most destructive thing that tab can do, so it gets a dialog. Mine said:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;code&gt;v1.0.0&lt;/code&gt; is deleted on origin. Anyone who has already fetched it keeps their copy, and a release built from it &lt;strong&gt;may survive&lt;/strong&gt; on the forge — this cannot be undone from here.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Read that again. "May survive" is not a warning; it is me not knowing, formatted to look like caution. And it is the sentence a person reads two seconds before doing something irreversible.&lt;/p&gt;

&lt;p&gt;The first half was cheap to settle without touching anything — &lt;code&gt;gh&lt;/code&gt; documents it in its own help text:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ gh release delete --help
FLAGS
      --cleanup-tag   Delete the specified tag &lt;span class="k"&gt;in&lt;/span&gt; addition to its release
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;em&gt;In addition to.&lt;/em&gt; Deleting a release leaves the tag standing; removing the tag as well is an explicit opt-in. And &lt;code&gt;gh release create&lt;/code&gt; says the mirror image: &lt;em&gt;"If a matching git tag does not yet exist, one will automatically get created."&lt;/em&gt; Two objects with an optional link, not two faces of one thing.&lt;/p&gt;

&lt;p&gt;The other direction — what happens to a &lt;strong&gt;release&lt;/strong&gt; when you delete its &lt;strong&gt;tag&lt;/strong&gt; — needed a real repository. So: a throwaway private repo, two annotated tags, two published releases.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ gh release list
v2.0.0  &lt;span class="nv"&gt;draft&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;  Release due
v1.0.0  &lt;span class="nv"&gt;draft&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;  Release uno

$ git push origin --delete refs/tags/v1.0.0
 - &lt;span class="o"&gt;[&lt;/span&gt;deleted&lt;span class="o"&gt;]&lt;/span&gt;         v1.0.0

$ gh release view v1.0.0 --json tagName,isDraft,url
&lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"isDraft"&lt;/span&gt;:true,&lt;span class="s2"&gt;"tagName"&lt;/span&gt;:&lt;span class="s2"&gt;"v1.0.0"&lt;/span&gt;,
 &lt;span class="s2"&gt;"url"&lt;/span&gt;:&lt;span class="s2"&gt;".../releases/tag/untagged-180ba3b4711b3e212eb7"&lt;/span&gt;&lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The release is &lt;strong&gt;not deleted&lt;/strong&gt;. GitHub demotes it to a &lt;strong&gt;draft&lt;/strong&gt; and re-homes it under an &lt;code&gt;untagged-…&lt;/code&gt; URL. It vanishes from the public releases page while still existing in the API.&lt;/p&gt;

&lt;p&gt;And then the measurement that actually changed the product:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ git push origin refs/tags/v1.0.0     &lt;span class="c"&gt;# put the tag back&lt;/span&gt;
$ gh release view v1.0.0 --json isDraft,url
&lt;span class="o"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"isDraft"&lt;/span&gt;:true,
 &lt;span class="s2"&gt;"url"&lt;/span&gt;:&lt;span class="s2"&gt;".../releases/tag/untagged-180ba3b4711b3e212eb7"&lt;/span&gt;&lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Still a draft. Restoring the tag does &lt;strong&gt;not&lt;/strong&gt; restore the release. Someone has to open GitHub and re-publish it by hand.&lt;/p&gt;

&lt;p&gt;So the honest sentence is not "it may survive". It is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;code&gt;v1.0.0&lt;/code&gt; is deleted on origin, and the release cut from it becomes a &lt;strong&gt;draft&lt;/strong&gt;: it disappears from the public releases page, and pushing the tag back does not bring it back — someone has to re-publish it by hand.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That is a different warning. The first one says &lt;em&gt;something bad might happen&lt;/em&gt;. The second one tells you what, and what it will cost to undo. It is also, incidentally, only computable because the tab already knows which tags carry a release — so a tag with none gets a shorter, calmer sentence, and a partially-loaded release list gets an explicit "this could not be checked here" instead of a guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the two have in common
&lt;/h2&gt;

&lt;p&gt;A test asserts. A dialog warns. Both are sentences that &lt;em&gt;look&lt;/em&gt; like knowledge, and neither is compiled, linted, or type-checked. The only thing standing between them and being wrong is whether somebody went and measured.&lt;/p&gt;

&lt;p&gt;The test was green because it never built the case it named. The dialog was hedged because I never ran the experiment. Same shape, ten minutes apart in the same afternoon — and the second one was easier to spot because the first had just cost me an hour.&lt;/p&gt;

&lt;p&gt;When you find yourself writing "may", "might", or "could" into user-facing copy about a destructive action, that is not caution. That is a to-do item wearing a disguise.&lt;/p&gt;




&lt;p&gt;This work is on a development branch and is not released yet — the current public build is &lt;strong&gt;FinderGit 0.30.0&lt;/strong&gt;. FinderGit is free, a Universal binary for Apple silicon and Intel, notarized by Apple, and needs macOS 15 or later.&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://findergit.app" rel="noopener noreferrer"&gt;https://findergit.app&lt;/a&gt; · Download: &lt;a href="https://findergit.app/download" rel="noopener noreferrer"&gt;https://findergit.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://zyvop.com/the-test-that-could-only-pass-and-the-warning-that-admitted-it-didn-t-know-plouj?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;💡 For more articles like this, &lt;a href="https://zyvop.com/newsletter?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication-footer" rel="noopener noreferrer"&gt;subscribe to the ZyVOP newsletter&lt;/a&gt;!&lt;/p&gt;

</description>
      <category>swift</category>
      <category>swiftui</category>
      <category>test</category>
      <category>coding</category>
    </item>
    <item>
      <title>octoscope 0.33.0 — the part of a pull request nobody reads line by line</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Tue, 08 Sep 2026 12:17:54 +0000</pubDate>
      <link>https://dev.to/undolog/octoscope-0330-the-part-of-a-pull-request-nobody-reads-line-by-line-35o4</link>
      <guid>https://dev.to/undolog/octoscope-0330-the-part-of-a-pull-request-nobody-reads-line-by-line-35o4</guid>
      <description>&lt;p&gt;You read the diff. The changed functions, the new test, maybe the workflow file. Then there is a four-hundred-kilobyte block of hashes at the bottom, and you scroll past it — because nobody reads that, and there is nothing in it a reviewer would recognise as suspicious anyway.&lt;/p&gt;

&lt;p&gt;Your lockfile is the one part of a pull request nobody reads line by line. octoscope 0.33.0 reads it for you.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyc1ekqodrbg11h0hhkz9.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyc1ekqodrbg11h0hhkz9.webp" alt="octoscope 0.33.0 — the Overview tab, banner reading the new version" width="800" height="706"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it can see now
&lt;/h2&gt;

&lt;p&gt;Since v0.27.0 the scan could tell you that something in &lt;em&gt;your own&lt;/em&gt; repository had started auto-executing — a hook that appeared, a workflow whose contents moved. It could not see the other half: a dependency that starts running code the moment you install it. That is not a new file and it is not a code change. It is a lockfile diff, and branch protection does nothing about it.&lt;/p&gt;

&lt;p&gt;Now the scan reads &lt;code&gt;package-lock.json&lt;/code&gt; (or &lt;code&gt;npm-shrinkwrap.json&lt;/code&gt;) on your default branch and compares the subset of your dependencies that carry an install script. Press &lt;code&gt;s&lt;/code&gt; on any repository in the Repos tab, exactly as before.&lt;/p&gt;

&lt;p&gt;Three things it can tell you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;a package that &lt;strong&gt;did not&lt;/strong&gt; run code at install and now does — something in your dependency tree began executing on your machine;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;the &lt;strong&gt;same version&lt;/strong&gt; whose content changed. That version was republished, and no upgrade explains it. It is the heaviest thing this part of the scan will say;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;an ordinary version bump, or a package that stopped running code at install. Both are listed, neither is scored.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why the subset, and not the whole file
&lt;/h2&gt;

&lt;p&gt;Because a lockfile changes constantly and the interesting part of it does not.&lt;/p&gt;

&lt;p&gt;I measured the last twenty revisions of the lockfile in three busy repositories — axios, npm/cli and undici, fifty-seven revisions in all. The files churned the entire time. The subset that runs code at install moved &lt;strong&gt;twice&lt;/strong&gt;. The same version was republished &lt;strong&gt;zero&lt;/strong&gt; times.&lt;/p&gt;

&lt;p&gt;That zero is the point. It is a measured rate of false alarms, not a guess, and it is what lets the sharp case actually mean something when it fires. An axis that goes off constantly is one you learn to skip, and then it is worth nothing on the day it is right.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does not check, it tells you
&lt;/h2&gt;

&lt;p&gt;This is npm only, and the report says so rather than going quiet. pnpm used to declare install scripts in its lockfile and dropped the field; Yarn never had one. Building on something that has already disappeared once would ship a rule that quietly decays, so if your lockfile is theirs, you get a line naming it and saying your dependency surface was &lt;strong&gt;not&lt;/strong&gt; compared.&lt;/p&gt;

&lt;p&gt;The same goes for a repository with no lockfile at all, one too large to read, or a format this scan has not measured. Silence would look exactly like &lt;em&gt;nothing here runs code at install&lt;/em&gt;, and that is the one thing it must never imply.&lt;/p&gt;

&lt;p&gt;And it never looks at the registry. The claim is that your dependencies' auto-execute surface &lt;em&gt;changed&lt;/em&gt; — never that a dependency is malicious. What to do about it is yours.&lt;/p&gt;

&lt;h2&gt;
  
  
  Upgrading
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew upgrade gfazioli/tap/octoscope
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or &lt;code&gt;gh extension upgrade octoscope&lt;/code&gt;, &lt;code&gt;go install github.com/gfazioli/octoscope@latest&lt;/code&gt;, or pull the container image.&lt;/p&gt;

&lt;p&gt;The first scan after upgrading will say it is the &lt;em&gt;first comparison&lt;/em&gt; of your dependency surface rather than claiming nothing changed — there is nothing recorded to diff against yet. The one after that is the one that talks.&lt;/p&gt;




&lt;p&gt;Site: &lt;a href="https://gfazioli.github.io/octoscope" rel="noopener noreferrer"&gt;https://gfazioli.github.io/octoscope&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Newsletter: &lt;a href="https://octoscope.substack.com" rel="noopener noreferrer"&gt;https://octoscope.substack.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Mastodon: &lt;a href="https://hachyderm.io/@undolog" rel="noopener noreferrer"&gt;https://hachyderm.io/@undolog&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://zyvop.com/octoscope-0-33-0-the-part-of-a-pull-request-nobody-reads-line-by-line-8x3b5?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;💡 For more articles like this, &lt;a href="https://zyvop.com/newsletter?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication-footer" rel="noopener noreferrer"&gt;subscribe to the ZyVOP newsletter&lt;/a&gt;!&lt;/p&gt;

</description>
      <category>babeltea</category>
      <category>cli</category>
      <category>github</category>
      <category>tui</category>
    </item>
    <item>
      <title>Netfox 0.19.0 — what a certificate says about itself</title>
      <dc:creator>Giovambattista Fazioli</dc:creator>
      <pubDate>Mon, 07 Sep 2026 10:03:08 +0000</pubDate>
      <link>https://dev.to/undolog/netfox-0190-what-a-certificate-says-about-itself-22n1</link>
      <guid>https://dev.to/undolog/netfox-0190-what-a-certificate-says-about-itself-22n1</guid>
      <description>&lt;p&gt;Every home network has a few of them: the NAS admin page, the printer's web UI, the router itself, a Home Assistant box. They all speak TLS, they all present a certificate, and almost nobody ever looks at it — until a browser refuses to open one and you are left guessing whether the device is broken, misconfigured, or just doing what home devices do.&lt;/p&gt;

&lt;p&gt;Netfox 0.19.0 reads that certificate for you and says what it says.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you will see
&lt;/h2&gt;

&lt;p&gt;Open a device, pick a port that speaks TLS from the first byte — 443, 8443, 993, 995 and their kind — and press Read certificate. The card underneath shows who the certificate was issued to, who issued it, and when it expires. Then it states the two things worth knowing without making you work them out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Expired.&lt;/strong&gt; Named as such, with the date.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Signed by itself.&lt;/strong&gt; Nothing vouches for it. That is normal on a home device that generated its own, and worth a second look anywhere else — and the card says exactly that, so the verdict arrives with its context.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two more lines appear only when they matter: a certificate that runs out within three weeks, and one that is not valid yet — which on a home network almost always means the clock on the device is wrong, not the certificate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1wtdjom83q2tq5mi8te.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1wtdjom83q2tq5mi8te.webp" alt="The service lookup on an open port. The certificate card sits right beside it, behind the same privacy switch." width="630" height="900"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The service lookup on an open port. The certificate card sits right beside it, behind the same privacy switch.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does not do
&lt;/h2&gt;

&lt;p&gt;It does not start anything on its own. The read happens when you press the button, and only if the same privacy setting that governs looking up service info is on. Ports that start in plain text and upgrade to TLS later are deliberately left alone: a greeting aimed at them is not a greeting.&lt;/p&gt;

&lt;p&gt;And in Demo Mode the card is hidden entirely. A certificate's name on a home network is very often the device's hostname, which is exactly the kind of thing Demo Mode exists to keep off a screenshot.&lt;/p&gt;

&lt;h2&gt;
  
  
  A correction
&lt;/h2&gt;

&lt;p&gt;The What's New panel of 0.18.1 said nothing in the app itself had changed. That was wrong, and the panel inside the app was the one place it could not be fixed on the day. Besides the signing fix, 0.18.1 also graded the radio's headroom by the same threshold the Wi-Fi tool uses, named the interface the route leaves through, and rewrote two sentences of the link panel. This release's panel says so.&lt;/p&gt;




&lt;p&gt;Netfox is free, a universal binary (Apple Silicon + Intel), runs on macOS 15.6+, and is signed and notarized.&lt;/p&gt;

&lt;p&gt;Netfox for macOS — Website: &lt;a href="https://netfox.app" rel="noopener noreferrer"&gt;https://netfox.app&lt;/a&gt; · Download: &lt;a href="https://netfox.app/download" rel="noopener noreferrer"&gt;https://netfox.app/download&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://zyvop.com/netfox-0-19-0-what-a-certificate-says-about-itself-qnygb?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication" rel="noopener noreferrer"&gt;ZyVOP&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;💡 For more articles like this, &lt;a href="https://zyvop.com/newsletter?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=syndication-footer" rel="noopener noreferrer"&gt;subscribe to the ZyVOP newsletter&lt;/a&gt;!&lt;/p&gt;

</description>
      <category>macos</category>
      <category>network</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
