Behavior tweaks for notifications

[begunfx]

Currently notifications are sent for new containers every time a check is run. It might make sense to have an option to only trigger the notification only 1x for each new update. Also this option should be granular enough to be separate for push notifications vs Gmail etc. Default update behavior is debatable as to whether it should be 1x or not. Thanks

[s-b-e-n-s-o-n]

Good news — this is already shipped.

1. "Notify once per new update":
Every trigger has a ONCE flag (DD_TRIGGER_{type}_{name}_ONCE=true), and true is the default. With it on, the trigger remembers which containers it already notified about and skips them on subsequent scans until the result actually changes. Docs: triggers configuration.

2. "Separate for push vs Gmail, etc.":
Each trigger is its own channel — you can configure a Gmail trigger with ONCE=true and a Pushover trigger with ONCE=false (or vice versa) independently. There's no single shared "notify once" switch because every trigger instance has its own setting.

If you're seeing repeated notifications for the same update, worth checking:

• Whether the affected trigger has ONCE=false explicitly set
• Whether you're on rc.7 or rc.8 — there was a batch+digest mode bug that re-fired the digest channel after the batch send (GMAIL: Batch and Digest Email Issues/Inconsistencies #282). Fixed in v1.5.0-rc.9.

Closing — ping back if you're still seeing repeats after confirming ONCE=true on the affected trigger.