check-issue-refs: blanket-ban tracker tags in markdown too, no exceptions

This commit is contained in:
damocles 2026-09-09 21:02:48 +02:00
commit e1e913015d
24 changed files with 81 additions and 89 deletions

View file

@ -43,7 +43,8 @@ It used to be otherwise, and the seam was real: each side had its own
`users.json` treated as authoritative, rendering the _same_ physical
`users.yml`. A writer whose own JSON was missing could not tell "nothing
here yet" from "someone else's users", so it refused to write at all —
which is exactly what a hive with existing users hit (#3422).
which is exactly what a hive with existing users hit
(`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3422`).
What still has to hold, since two processes share the file: