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

@ -95,7 +95,8 @@ store's container reads it, writes the `swarm-controller` policy, enables the
cert auth method, and creates the `swarm-controller` role that attaches the two.
⚠️ **This has only run once, and it didn't go all the way through.** The
first real provision against a live store returned 403 (#4124), so
first real provision against a live store returned 403
(`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/4124`), so
treat the block above as derived-then-partly-tested rather than proven: the
grants still come from `-output-policy`, not from a swarm that came up on them.
What that 403 does _not_ tell you is whether the login or the write was
@ -128,7 +129,8 @@ can't hand you, being what opens it. ⚠️ Not the gateway's HTTPS certificates
store that took its identity from an authority it will itself distribute could
never come up before that authority.
Making even the `init` unnecessary is tracked in issue #3768.
Making even the `init` unnecessary is tracked in
`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/3768`.
### 4 · Swarm SSO (only when `deploy.authelia`)