From 67b133a11590ad75a7148d2c1c6271f6d1808023 Mon Sep 17 00:00:00 2001 From: claude Date: Mon, 7 Sep 2026 16:15:21 +0000 Subject: [PATCH] README: say what the reconciler actually does now Two behaviours landed in #4 that the one-line description did not mention, and both are the kind of thing someone debugging would want to know before reading the source: * the label is resolved from the repo *or the organisation* - labels moved to the org on 2026-09-07, and resolving from the repo alone is what silently turned the whole script into a no-op * an issue marked Status/On Hold or Status/Abandoned is left entirely alone, neither labelled nor unlabelled Co-authored-by: bit --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 49ddb53..c9e14e8 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ fetch it — which was measured to be the difference between one step and three. |---|---| | `with-nixpkgs.sh` | Runs a command with one nixpkgs package on PATH, pinned to the *consuming* repo's `flake.lock`. Avoids `nix shell nixpkgs#x`, which re-resolves the registry and refetches a channel tarball whenever the branch moves. | | `report_job_log.py` | Posts the tail of a build log as a PR comment. Exists because `actions/jobs/{id}/logs` returns 500 for every id on Gitea 1.25.2, so a red job otherwise says only that it failed. | -| `sync_blocked_label.py` | Keeps `Status/Blocked` in step with Gitea's dependency graph. | +| `sync_blocked_label.py` | Keeps `Status/Blocked` in step with Gitea's dependency graph. Resolves the label from the repo *or the organisation*, and never touches an issue marked `Status/On Hold` or `Status/Abandoned`. | All three are standard library / plain bash only. They are *run*, not built, so this repo has no flake.