Notify sneak's ntfy topic on every CI deploy #48

New Issue

2026-11-05T20:41:02+01:00

clawbot commented

2026-11-05 20:41:02 +01:00

sneak, 2026-11-05 in chat: "on every repo that does automatic deployments via CI, update CI to notify the ntfy topic [the topic he named, kept out of this public tracker]"

Only sneak.berlin and lora.vegas deploy from CI. The topic is read from the Actions secret NTFY_TOPIC and is never written in the repository or on the tracker, because anyone who knows it can read and send these notifications. sneak adds the secret.

Definition of done:

.gitea/workflows/deploy.yml gets a last job, notify, that needs every other job, runs whether they passed or failed (if: always()), and posts one message with curl to https://ntfy.sh/ followed by the topic from secrets.NTFY_TOPIC.
On success the message title says lora.vegas deployed and from which branch, and the body gives the short commit and the address it deployed to. On failure the title says the deploy failed, the message has high priority, and the body links to the failed run.
The notify job never fails a deploy that worked: a notification that cannot be sent leaves the deploy's result as it was.
One commit ending (closes #N), PR into next; make check passes.

Model: opus-5-5

sneak, 2026-11-05 in chat: "on every repo that does automatic deployments via CI, update CI to notify the ntfy topic [the topic he named, kept out of this public tracker]" Only `sneak.berlin` and `lora.vegas` deploy from CI. The topic is read from the Actions secret `NTFY_TOPIC` and is never written in the repository or on the tracker, because anyone who knows it can read and send these notifications. sneak adds the secret. Definition of done: - `.gitea/workflows/deploy.yml` gets a last job, `notify`, that needs every other job, runs whether they passed or failed (`if: always()`), and posts one message with `curl` to `https://ntfy.sh/` followed by the topic from `secrets.NTFY_TOPIC`. - On success the message title says `lora.vegas` deployed and from which branch, and the body gives the short commit and the address it deployed to. On failure the title says the deploy failed, the message has high priority, and the body links to the failed run. - The `notify` job never fails a deploy that worked: a notification that cannot be sent leaves the deploy's result as it was. - One commit ending `(closes #N)`, PR into `next`; `make check` passes. Model: opus-5-5

clawbot referenced this issue from a commit

2026-11-05 21:02:56 +01:00

Notify sneak's ntfy topic on every CI deploy (closes #48)

clawbot referenced a pull request that will close this issue

2026-11-05 21:03:11 +01:00

Notify sneak's ntfy topic on every CI deploy (closes #48) #49

clawbot commented

2026-11-05 21:03:26 +01:00

Added a notify job to the deploy workflow that posts one ntfy message on every deploy: success sends "lora.vegas deployed from main" with the short commit and https://lora.vegas/, failure sends a high-priority "lora.vegas deploy failed" with a link to the failed run. The topic comes only from secrets.NTFY_TOPIC and is never written in the repository; the job runs with if: always() and continue-on-error so it cannot change a deploy's result.

Model: deepseek-v4-pro

Added a notify job to the deploy workflow that posts one ntfy message on every deploy: success sends "lora.vegas deployed from main" with the short commit and https://lora.vegas/, failure sends a high-priority "lora.vegas deploy failed" with a link to the failed run. The topic comes only from secrets.NTFY_TOPIC and is never written in the repository; the job runs with if: always() and continue-on-error so it cannot change a deploy's result. Model: deepseek-v4-pro

clawbot referenced this issue

2026-11-05 21:15:48 +01:00

Notify sneak's ntfy topic on every CI deploy (closes #48) #49

clawbot referenced this issue from a commit

2026-11-05 21:22:54 +01:00

Notify sneak's ntfy topic on every CI deploy (closes #48)

clawbot referenced this issue from a commit

2026-11-05 23:26:49 +01:00

Notify sneak's ntfy topic on every CI deploy (closes #48)

clawbot closed this issue

2026-11-05 23:51:40 +01:00

clawbot referenced this issue from a commit