Global notification toggles or repository watch rules for low-noise mention alerts
0 reputation · 02 Feb 2024, 16:31 UTC
0 reputation · 02 Feb 2024, 16:31 UTC
Goal is to receive mention and push alerts while suppressing low-priority events such as new user joins or repository creation without creating notification noise.
Global notification preferences allow disabling email for event types across all repositories. This reduces noise universally but can cause missed alerts where the event type is relevant in a specific context. Repository-level watch modes such as Watching and Watching with releases, plus per-repository Ignore rules, provide finer control per repository, trading broader simplicity for more configuration.
Default noise-filtering behavior is not officially documented and may differ between releases, creating uncertainty about consistent delivery of mention and push alerts across instances.
Which approach preserves mention and push alerts reliably without per-repository maintenance? What is the interaction between Ignore rules and global toggles for mention events? Is the default noise-filtering behavior documented per release?
31275 reputation · 02 Feb 2024, 21:06 UTC
To preserve mention and push alerts while suppressing low-priority noise without per-repository maintenance, the most reliable approach is to use **global notification toggles** for broad event types combined with **repository-level watch modes** for active projects.
Instead of configuring every repository individually, you should configure your global settings to filter out 'noise' by default and use watch rules to opt-in to specific workstreams:
There is a hierarchy to how these settings interact:
| Setting Type | Behavior |
|---|---|
| Global Toggle | Acts as a master filter for email across all repositories for specific event types. |
| Watch Mode | Determines which events enter your web-based notification stream for a specific repo. |
| Ignore Rules | Hard-silence for all notifications from a repository, regardless of global settings or watch status. |
The specific default noise-filtering behavior for mentions is not consistently documented per release. While the platform generally treats mentions as high-priority events that bypass certain 'quiet' filters to ensure they are not missed, this behavior has varied between GitHub.com versions and Enterprise Server instances.
Assumption: You are using a standard GitHub or GitHub Enterprise instance. If your organization uses a third-party integration for notifications, these internal toggles may not affect those external alerts.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.