I would move the mails to commits so they are "archived". Github has a really good working inbox feature, there is not really a need to have PR mails on the dev list.
The aggregated dependabots PRs are a PITA as they tend to clog up on a regular basis especially on bigger projects and because of BS mail is the worst reason to switch. So just move the mails to commits or a new list "prs" and use the inbox feature of github to track PRs (When you work with github this is/should be your standard workflow anyway). - Sebastian On 2025/06/02 07:31:52 Christofer Dutz wrote: > Hi all, > > when having a look at this list, it generally contains 99% emails of people > merging pull requests issued by dependabot. > I know we’re redirecting the initial emails elsewhere, but still the > remaining flood of dependabot pr emails is quite annoying. > I have switched to a mode where I simply mark them and delete them, but for > others this will be one of the reasons to not react to emails. > > Should we move all PR related emails elsewhere at the risk of missing the > occasional legit PR? > > Is there another way? > > I personally like the aggegated dependabot PRs other projects are getting. I > know you loose the fine granularity, but you get rid of this continuous > stream of BS emails. > > Chris >
