Disable Notifications For Team Mentions

[mpiggott]

I've been added to a couple teams for permission for occasional contribution though I don't participate in the daily development on their repositories. This automatically subscribes you to mentions of the team, and as far as I can tell there seems to be no method to unwatch the team.

To me it would make sense to have allow users to unwatch a team, rather than needing to maintain parallel permission structures, i.e. team-x and friends-of-team-x where the permissions are identical but the latter wouldn't be tagged.

[alex-steinberg]

🎉 +1 ^^! What's more is that a review can be requested from a team and that subscribes the team to that PR. So a team of 10 could have one or two members actually pick up the code review, but all 10 are sent notifications for every.single.comment because the request was aimed at the team. There must be a better, less noisy way to do this.

[dominicfraser]

👍 This is also similar to what is described in https://github.com/orgs/community/discussions/35673 too, "Enable code ownership without automatic PR notifications for entire teams", and https://stackoverflow.com/questions/72534373/how-to-enforce-review-from-codeowners-without-automatically-requesting-a-review

the desired flow for a contributer is something like this:
open a pull request -> mess around, make changes -> manually request a review when ready (can't merge without codeowner approval)

[VcSaJen]

GitHub user sends notification to 400000 users
Github needs to implement it ASAP

[ajkerzner]

There should be optional limits when mentioning a target team or whatever that has, say, 500+ members. This is very much like when someone emails a Microsoft Teams email chain and ends up emailing up to 25,000 people. When the number of potential recipients goes up, the risk of misuse goes up. Find a solution.

[AntonioND]

Please, this would be very helpful. Right now my notifications are always so noisy that they are useless.

[joshuasimon-taulia]

please stop the noise

[jdevfullstack]

I'm not very sure whether this is a solution, in watching the repo, there are now choices and custom ones

and at your personal settings

you can uncheck automatically watch repo when you were given access and simply customize it

[AntonioND]

@jdevstatic this is not a fix. I'm added as reviewer to every single PR in my team because my team is added as required reviewer. This bypasses per-repository settings, they are direct notifications to all team members.

[fendent]

This is essentially non-optional. I work with hundreds of repositories in our org where teams are used as a permission system. I get notifications for every single PR that comes in for these repos, despite whatever notification settings has been made.

[juanswan13]

The same issue for me, at the end I created a rule in my email to send to a different folder all the emails coming from GitHub, and also created a rule that empties the folder after a week. Because of the noise, I'm not checking GitHub emails anymore which is an issue when I actually need to review something !!

[willacai]

@mpiggott do you have the "Automatically watch teams" setting turned on? This will remove notifications when the team is mentioned in comments, but not for when the team is requested for code review as others have mentioned.

For anyone struggling with being bombarded by your team's code review notifications, the Maintainer(s) of a team can set certain team members as Code Owners, and set certain team members to never be notified. See the docs on Managing code review settings for your team:

Direct link to Configuring Team Notifications how-to: https://docs.github.com/en/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team#configuring-team-notifications

[rcomer]

The description of the above "automatically watch teams" setting suggests that this only applies to teams you join in future. Is there another setting I'm missing that affects notifications for teams I'm already in?

[AntonioND]

While that is good to know, we need a setting that the user can set without requiring the owner of the team doing it.

[willacai]

Yup; on top of that, the "Never assign" setting is only an option when the Auto Assignment is turned on. This definitely requires a lot of active decisions and discussion within a team, which may be what Github is trying to encourage, but doesn't suit a lot of team use cases.

[Ganitzsh]

Running into the same issue, that'd be great to have a setting to only get notified when directly mentioned, and not anytime the team is added as a reviewer for every PR.

[rachellejensen]

Still facing the same issue. Different teams have different processes, and in a mono repo this doesn't make sense at the repo/maintainer level. It's a team setting based on how the team works!

[Rydez]

I'd also like to up vote this. In the case of a mono repo this is pretty unacceptable. My emails/notifications have more than a 5:1 noise to signal ratio.

[MrTemple]

How in great git's ghost is it STILL not possible to silence email alerts sent to an entire team?!

[bendb-instacart]

Please help :(

My phone is blowing up every minute with these pointless broadcasts

[nessex]

This is a big problem in monorepo situations where you have an admin team that has permissions across the whole repo. That admin team receives mentions on every single PR. It's only relevant to part of the problem described in the top post, but I'd love some granular controls within CODEOWNERS for this. For example:

* @my-org/admins
/services/service-a @my-org/service-a-team @my-org/admins!no-review-request

The syntax is just an example... But this would allow the admin team to actually make use of GitHub Notifications for their own tasks elsewhere in GitHub.

[rsamborski]

Same issue here. Please implement a solution to this.

[Naphier]

Even if you set the rule to assign to a user but not notify the team then it still notifies the team. Then proceeds to notify the team for every action on the PR. How annoying... Please make this better. Guess I'm moving to Probot for now.

[mryanprice]

Please implement some solution for this. My options are to be spammed with useless notifications or miss important notifications. If I could get notifications for just my own username instead of the team, it would resolve this for me.

[sethhochberg]

This is exactly what I'm looking for, as well. This problem becomes much more bearable if I can turn off notifications for the entire team's tag but ensure I am still notified for direct @ tags at me individually. If my team is requested as a reviewer and a colleague grabs the review, I don't need to continue seeing every action taken on that PR into eternity.

[mefryar]

Notifications for Team @mentions can now be disabled... but not notifications related to PR review requests 😞

Team Maintainers may now disable notifications resulting from a team @mention in GitHub issue and pull request comments through an optional configuration in the team settings page. Notifications resulting from PR review requests are unaffected by this setting.

[dgoldstein0]

I also have this exact same problem and am feeling huge pain now. My company

• uses a monorepo
• has lots of code ownership, with required reviews. so we're using CODEOWNERS & Teams.
• has people with different opinions on notification settings (e.g. slack vs email, whether to be notified only when you are mentioned vs when your team's code is touched etc)
• we also have our own bot for autoassigning reviewers, which kicks in asynchronously. the main difference between it and our built-in options are that it uses pagerduty schedules to assign to the current oncall for the team.

I flipped off the "automatically watch teams" option and it didn't do anything as far as I could tell - it certainly did not stop the notifications I am trying to get rid of.

I am shocked it is not possible for me to navigate to each of my teams and disable email notifications for when our review is requested. I am tempted to start marking these emails as spam.

[Ray-Eldath]

It's already halfway to 2024, can't believe GitHub still still still doesn't support mute team motifications and organizational name

Two seminal features for GitHub to be used as central code host for companies. Organization name stays on the most requested feature in the entire Profile category and notification system is one of the most important components in GitHub. Not even a single answer or comment from GitHub staffs, no, nothing.

[holograph]

Preach!

[NitzanSirota]

Coming from a relatively big company that has a huge number of monorepos and CODEOWNERS files, this is just terrible.
We either choose to dismiss all github notifications or getting bombarded with tons of PR threads that are not remotely related to us.

[holograph]

This is also a problem for medium-sized organizations with many repositories (and no monorepos). You always end up with a "superteam" for admins or principal-types, who tend to focus on one or two repositories at a time; disabling the "automatically watch teams" doesn't do much and the deluge of irrelevant PR notifications buries everything else.

GitHub, this is a real problem. Please address it!

[fusion2004]

Dittoing a lot of the above... recently added to a team whose approval is required for changing certain files via CODEOWNERS, and I do not want notifications for those PRs. We have manual processes for getting those reviews and it make notifications very noisy and harder to find the ones from my immediate team that I need to address.

Maybe a priority system, either in addition to or instead of a disabling system, would be ideal here. I wouldn't mind getting those notifications if I could filter them out and only check them every day or two.

[ianks]

Yeah this is definitely a pain point...

[satejbidvai]

Has this been solved?

[msdsk-quinyx]

In our org the team is added as a reviewer to every PR as a code owner. On top of that, we have a PR review lottery that requests reviews from an individual and only that individual is actually expected to review the code. Now, I need a way to sort through what is the useless team notifications from personal assignments - but they're both just "review requested". So, yeah, ditto.

[alexkatja]

This is a pain point for us as well. Please offer the ability to have the permissions and abilities of a team, but not receive notifications of all team mentions.