ci on Abbreviatory.com https://abbreviatory.com/tags/ci/ Recent content in ci on Abbreviatory.com Hugo -- gohugo.io en-us Wed, 04 Nov 2026 00:00:00 +0000 Abbreviatory Now Tracks New Warnings and Runs as a GitHub Action https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/ Wed, 04 Nov 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-now-tracks-new-warnings-and-runs-as-a-github-action/ Warnings pile up. A build has forty of them, everyone stopped reading them months ago, and the one that matters, the deprecation that turns into an error next quarter, arrives as number forty-one. Abbreviatory has always kept warnings in its report. Until now it didn’t say which ones were new. v0.6.0 does, behind a flag. Run with -warnings and a history, and the report compares warnings with the last run the way it already compares failures. How to Show What Changed Since the Last Run in a GitHub Actions Job Summary https://abbreviatory.com/how-to-show-what-changed-since-the-last-run-in-a-github-actions-job-summary/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-to-show-what-changed-since-the-last-run-in-a-github-actions-job-summary/ A red build on GitHub Actions usually means scrolling. The job log holds thousands of lines, the failures are somewhere in the middle, and the first question is always the same: did this break just now, or has it been broken for a week? The log can’t say. It only knows about this run. Abbreviatory can, if it keeps a history. Put abbreviatory run in front of the test command and send its report to the job summary. Abbreviatory 0.2 Tells You What Changed Since the Last Test Run https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ Sun, 18 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.2-tells-you-what-changed-since-the-last-test-run/ The first release made one run’s output short. This one compares it with the run before. Abbreviatory v0.2.0 keeps a history per command, and every report now opens with what changed: which failures are new, which got fixed, which are still failing and for how long, and which tests are flaky. Most CI runs aren’t news. The same three tests failed yesterday and they fail today. Reading the full report again, or having a coding agent read it again, mostly confirms what everyone already knows.