flan/truenas-truecloud-patch
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 12 Wiki Activity

A change to the publisher did not re-run the check
CI / shell (shellcheck + syntax) (push) Successful in 9s
Details
CI / python 3.11 (push) Failing after 13s
Details
CI / python 3.12 (push) Failing after 13s
Details
CI / python 3.13 (push) Failing after 11s
Details
TrueNAS compatibility / compat (push) Successful in 9s
Details

Browse Source 
compat.yml's push paths listed tools/compat.py but not tools/compat_publish.py.
So the commit that taught the bot to refresh a stale report body fired no run, and
the report stayed stale until the next scheduled one -- caught by watching for the
run that never came. A fix nobody runs is a fix nobody has.
This commit is contained in:
flan
2026-07-14 03:06:44 +00:00
parent 6ce1206f01
commit 6b7034a8cd
2 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/compat.yml
+5
View File
@@ -24,6 +24,11 @@ on:
paths:
# The manifest itself changed -- re-check immediately rather than waiting a day.
- "tools/compat.py"
# ...and so did the thing that PUBLISHES the finding. This was missing, and it
# showed: the commit teaching the bot to refresh a stale report body touched only
# compat_publish.py, so no run fired, and the report stayed stale until the next
# scheduled one. A fix nobody runs is a fix nobody has.
- "tools/compat_publish.py"
- ".github/workflows/compat.yml"
permissions: