On a normal GitHub project, you’d only be notified once. Instead, we’re getting personal emails, list emails, Jira emails (to both personal emails and list emails), needless rebasing on a branch (!!), and pinging every single Jira issue in the rebased history. It’s spamming over ten emails where one is sufficient.
— Matt Sicker > On Sep 24, 2022, at 01:23, Gary Gregory <garydgreg...@gmail.com> wrote: > > Maybe this discussion should take place in a Dependabot ticket? We can't > change it here ;-) > > Gary > >> On Fri, Sep 23, 2022, 22:39 Matt Sicker <boa...@gmail.com> wrote: >> >> The messenger only needs one email per update. I’m getting several for >> each one. I can’t even tell if humans are contributing anything anymore. >> >> — >> Matt Sicker >> >>>> On Sep 23, 2022, at 17:06, Gary Gregory <garydgreg...@gmail.com> wrote: >>> >>> Have you ever heard the expression "Don't shoot the messenger"? ;-) >>> >>> Dependabot is a great tool IMO. >>> >>> I think someone had proposed a different email address for bot emails >> that >>> that obviously did not happen. Then there is classic "inbox rules" reply. >>> Whomever wants to drive this can go ahead... >>> >>> Gary >>> >>>> On Fri, Sep 23, 2022, 19:47 Matt Sicker <boa...@gmail.com> wrote: >>>> >>>> After secretary emails, emails related to Dependabot are the next most >>>> common message in my mailbox. I’ve already had to clear out several >> gigs of >>>> emails, and these Dependabot rebases and relentless updates are making >> it >>>> impossible to follow anything on the mailing lists anymore. >>>> >>>> Proposal: all Dependabot messages should be batched into a digest email >> or >>>> similar. I don’t need multiple notifications per PR, and I don’t need >>>> dozens of Jira issues commented on for no good reason. Alternative: >> disable >>>> Dependabot as a failed experiment. >>>> >>>> — >>>> Matt Sicker >>
