Notification delivery: fire-and-forget with no retry #62
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Notifications are fire-and-forget (goroutines, no retry). If Slack/ntfy is temporarily down, changes are silently lost.
Consider: retry with backoff, or at minimum log notification failures prominently.
Ref: issue #5 item 10