Notify sneak's ntfy topic on every CI deploy (closes #48)
check / check (push) Successful in 2m54s
check / check (push) Successful in 2m54s
Add a notify job to the deploy workflow that posts an ntfy message on success or failure, using the topic from secrets.NTFY_TOPIC. Model: deepseek-v4-pro
This commit is contained in:
@@ -34,6 +34,16 @@ leaning on `.gitignore` (https://git.eeqj.de/sneak/lora.vegas/issues/33).
|
||||
|
||||
# Completed Steps
|
||||
|
||||
- 2026-11-05: added a `notify` job to the deploy workflow that posts an ntfy
|
||||
message on every deploy, success or failure (closes
|
||||
https://git.eeqj.de/sneak/lora.vegas/issues/48). The job runs `if: always()`
|
||||
so it fires whether the build and deploy passed or failed, and the Notify step
|
||||
carries `continue-on-error: true` so a notification that cannot be sent leaves
|
||||
the deploy's result exactly as it was. On success the message body is the
|
||||
short commit plus the site URL, and on failure it is a link to the run. The
|
||||
topic comes from the `NTFY_TOPIC` Actions secret, which sneak must add before
|
||||
anything is sent; the topic is never written in the repository. Both curl
|
||||
calls carry `--max-time 10` so a stalled ntfy cannot hold the run open
|
||||
- 2026-10-21: made `script/lint` fail when two pages write the same output path
|
||||
(https://git.eeqj.de/sneak/lora.vegas/issues/25). `Dockerfile.lint` now runs
|
||||
`hugo --minify --printPathWarnings --panicOnWarning`. `--printPathWarnings`
|
||||
|
||||
Reference in New Issue
Block a user