steve/restic-manager
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 1 Wiki Activity

feat(channels): include event verb in ntfy title + smtp subject #10

Merged
steve merged 1 commits from alerts-channel-event-clarity into main 2026-05-04 23:25:39 +01:00
Conversation 0 Commits 1 Files Changed 4
+38 -7

1 Commits

Author SHA1 Message Date
steve 43e72b0d5b feat(channels): include event verb in ntfy title + smtp subject
CI / Build (windows/amd64) (pull_request) Successful in 30s
Details
CI / Build (linux/amd64) (pull_request) Successful in 23s
Details
CI / Build (linux/arm64) (pull_request) Successful in 22s
Details
CI / Lint (pull_request) Successful in 1m19s
Details
CI / Test (linux/amd64) (pull_request) Successful in 1m42s
Details 
Raise / ack / resolve all rendered with the same title and body on
ntfy and SMTP, so a recovery looked identical to the original alert.
Webhook was already fine because the JSON envelope carries 'event'.

ntfy:
  Title  '[raised · warning] dev backup_failed' (was '[warning] …')
  Tags   'raised,warning,backup_failed' (was 'warning,backup_failed')
  Body   'Resolved · <message>' / 'Acknowledged · <message>' on those events
SMTP:
  Subject '[restic-manager] [raised · warning] dev: backup_failed'

Plus: cmd/_fake_alert now accepts the ref as a positional argument
(go run ./cmd/_fake_alert steve-001) instead of silently ignoring
unknown positional args. Refuses ambiguous '-ref X positional Y'.
 2026-05-04 23:17:42 +01:00