chadtmiller.com/knotless

Switch repository

Loading…

What changes

The triage bot labels as triage.knotless.dev (did:plc:hwfywp7r4cfumv54v2xk3jz7), an account of knotless's own on its own pds.js worker, as the runner (ci.knotless.dev) and the reviewer (review.knotless.dev) do. KNOTLESS_BOT_DIDS names it in place of the old bot, bigmoves.spaces-alpha.bsky.network, so it logs in at /oauth/bot for private repositories. deploy/main.tf's note on the handles names the triager's.

Why

The triager labels for every repository that names it, so it belongs to knotless, not to the owner's spaces-alpha account. The old account's handle had also stopped resolving: its well-known is served under a certificate for spaces-alpha.host.bsky.network only, and knotless-triage was exiting at start, 67 restarts and counting.

How it was checked

Already done on prod by hand: the old bot's 51 dev.knotless.label records were copied to the new account under the same keys, unchanged (judged with them, so nothing is judged again), /etc/knotless/triage.env logs in as the new account (the old kept as triage.env.bak-bigmoves), and chadtmiller.com/knotless names the new account a triager of kind and area in place of the old. triage has run without restarting since, and an issue the old bot labelled shows the same labels from the new account. No other repository named the old bot (listRepos?triager=).

Changeset: none

Shortcomings

The _atproto.triage TXT record is not made yet: the Cloudflare token refuses this Mac's address. Until it is, the account's handle in its DID document is its workers.dev name; triage.knotless.dev already serves /.well-known/atproto-did. The handles map in the deploy tfvars names triage, so the next apply makes the record.

🤖 Generated with Claude Code

This swaps the old triager DID for did:plc:hwfywp7r4cfumv54v2xk3jz7 in KNOTLESS_BOT_DIDS in the deploy workflow. It also adds the triager to the handles comment in deploy/main.tf. The change is small and matches the description. The first DID and the last (runner and reviewer) are unchanged, and the old bot's DID is dropped. I found no problems. The pending _atproto.triage TXT record is documented in the body and is made by the next apply. I only read the diff, so I did not check the prod state it describes.