From ab0b66c47da5fa0b0b55049a7f8ff81de721198a Mon Sep 17 00:00:00 2001 From: sudolulo Date: Mon, 13 Jul 2026 19:02:57 +0000 Subject: [PATCH] compat: the bug-report title must be stable across ref-set changes The title embedded the list of broken refs, so the issue's identity changed whenever that set changed -- and it did: when the async/sync port briefly made 26 look green, the next run filed a SECOND issue for 'master' alone. A bot that spawns duplicates gets muted, and then it is not a warning system any more. The title is now fixed; the refs live in the body, which gets updated in place. --- .github/workflows/compat.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/compat.yml b/.github/workflows/compat.yml index 6b82622..1c93a94 100644 --- a/.github/workflows/compat.yml +++ b/.github/workflows/compat.yml @@ -170,7 +170,7 @@ jobs: if: ${{ steps.report.outputs.broken == '1' && contains(github.server_url, 'github.com') }} env: GH_TOKEN: ${{ github.token }} - TITLE: "Incompatible with upcoming TrueNAS: ${{ steps.report.outputs.refs }}" + TITLE: "TrueNAS compatibility: the patch's assumptions no longer hold" run: | # One issue per set of broken refs, reopened/updated rather than duplicated # daily -- a bot that files the same issue every morning gets muted, and @@ -191,7 +191,7 @@ jobs: env: TOKEN: ${{ secrets.GITEA_TOKEN || github.token }} API: ${{ github.server_url }}/api/v1/repos/${{ github.repository }} - TITLE: "Incompatible with upcoming TrueNAS: ${{ steps.report.outputs.refs }}" + TITLE: "TrueNAS compatibility: the patch's assumptions no longer hold" run: | # python3, not jq: jq is not guaranteed on a self-hosted runner, and a bug # report that dies on a missing tool is a warning system that does not warn.