Re: Dependabot emails are filling my mailbox
Seems like that fixed the issue. Carry on,, Dependabot! — Matt Sicker > On Sep 25, 2022, at 11:12, Matt Sicker wrote: > > I tried disabling Jira propagation before via that file, though it still > seems to be enabled. We have talked a little before about migrating to GitHub > Issues, though nothing concrete yet. Guess I’ll file an Infra ticket about > the issue. > > — > Matt Sicker > >>> On Sep 25, 2022, at 04:16, Vladimir Sitnikov >>> wrote: >>> >> Alternative options could be: >> >> a) Divert GitBox notifications to a separate mailing list (e.g. >> issues-gitbox@) which no one really subscribes. >> The key issue with GitBox notifications is that it produces messages that >> do not group by subject, >> so 5 notifications on a single PR might look like 5 different emails. >> See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss >> Personally, I use GitHub notifications as it enables me to subscribe or >> mute issues/PRs individually, >> and I believe the only viable reason for having GitBox notifications is for >> archiving purposes (== write-only). >> >> b) Disable propagating PR comments to JIRA comments. >> See >> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions >> >> c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. >> That would resolve "PR comments are duplicated in JIRA" issue. >> Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub >> Issues, and Apache Lucene >> recently migrated from JIRA to GitHub Issues, so the migration is an option >> indeed. >> >> Vladimir
Re: Dependabot emails are filling my mailbox
Alright, I found the setting related to this and disabled it. Hopefully this will address most of the Dependabot noise and make the tool useful again! — Matt Sicker > On Sep 23, 2022, at 18:46, Matt Sicker 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
Re: Dependabot emails are filling my mailbox
Just filed https://issues.apache.org/jira/browse/INFRA-23722 — Matt Sicker > On Sep 25, 2022, at 11:12, Matt Sicker wrote: > > I tried disabling Jira propagation before via that file, though it still > seems to be enabled. We have talked a little before about migrating to GitHub > Issues, though nothing concrete yet. Guess I’ll file an Infra ticket about > the issue. > > — > Matt Sicker > >>> On Sep 25, 2022, at 04:16, Vladimir Sitnikov >>> wrote: >>> >> Alternative options could be: >> >> a) Divert GitBox notifications to a separate mailing list (e.g. >> issues-gitbox@) which no one really subscribes. >> The key issue with GitBox notifications is that it produces messages that >> do not group by subject, >> so 5 notifications on a single PR might look like 5 different emails. >> See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss >> Personally, I use GitHub notifications as it enables me to subscribe or >> mute issues/PRs individually, >> and I believe the only viable reason for having GitBox notifications is for >> archiving purposes (== write-only). >> >> b) Disable propagating PR comments to JIRA comments. >> See >> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions >> >> c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. >> That would resolve "PR comments are duplicated in JIRA" issue. >> Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub >> Issues, and Apache Lucene >> recently migrated from JIRA to GitHub Issues, so the migration is an option >> indeed. >> >> Vladimir
Re: Dependabot emails are filling my mailbox
I tried disabling Jira propagation before via that file, though it still seems to be enabled. We have talked a little before about migrating to GitHub Issues, though nothing concrete yet. Guess I’ll file an Infra ticket about the issue. — Matt Sicker > On Sep 25, 2022, at 04:16, Vladimir Sitnikov > wrote: > > Alternative options could be: > > a) Divert GitBox notifications to a separate mailing list (e.g. > issues-gitbox@) which no one really subscribes. > The key issue with GitBox notifications is that it produces messages that > do not group by subject, > so 5 notifications on a single PR might look like 5 different emails. > See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss > Personally, I use GitHub notifications as it enables me to subscribe or > mute issues/PRs individually, > and I believe the only viable reason for having GitBox notifications is for > archiving purposes (== write-only). > > b) Disable propagating PR comments to JIRA comments. > See > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions > > c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. > That would resolve "PR comments are duplicated in JIRA" issue. > Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub > Issues, and Apache Lucene > recently migrated from JIRA to GitHub Issues, so the migration is an option > indeed. > > Vladimir
Re: Dependabot emails are filling my mailbox
Alternative options could be: a) Divert GitBox notifications to a separate mailing list (e.g. issues-gitbox@) which no one really subscribes. The key issue with GitBox notifications is that it produces messages that do not group by subject, so 5 notifications on a single PR might look like 5 different emails. See https://lists.apache.org/thread/xk18m7sp46z7d86pwtkvn69mnb906hss Personally, I use GitHub notifications as it enables me to subscribe or mute issues/PRs individually, and I believe the only viable reason for having GitBox notifications is for archiving purposes (== write-only). b) Disable propagating PR comments to JIRA comments. See https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions c) Allow JIRA-less PRs, or even migrate from JIRA to GitHub issues. That would resolve "PR comments are duplicated in JIRA" issue. Jokes aside, I've just migrated Apache JMeter from Bugzilla to GitHub Issues, and Apache Lucene recently migrated from JIRA to GitHub Issues, so the migration is an option indeed. Vladimir
Re: Dependabot emails are filling my mailbox
What filters did you set up? That might be a sufficient fix. — Matt Sicker > On Sep 25, 2022, at 00:05, Ralph Goers wrote: > > Dependabot really doesn’t need to generate ANY emails. Every time it commits > something to Github, including creating PRs, we already will get an email for > that. > So the dependabot emails are just annoying noise. That is why I configured my > email server to discard them all last week. > > Now, instead of getting hundreds of emails seemingly every day from Commons, > Maven and Logging I am down to a manageable number. And the ones I now get > are because a human did something that warrants human attention. > > Ralph > >> On Sep 23, 2022, at 5:05 PM, Gary Gregory 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 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 >
Re: Dependabot emails are filling my mailbox
Dependabot really doesn’t need to generate ANY emails. Every time it commits something to Github, including creating PRs, we already will get an email for that. So the dependabot emails are just annoying noise. That is why I configured my email server to discard them all last week. Now, instead of getting hundreds of emails seemingly every day from Commons, Maven and Logging I am down to a manageable number. And the ones I now get are because a human did something that warrants human attention. Ralph > On Sep 23, 2022, at 5:05 PM, Gary Gregory 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 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
Re: Dependabot emails are filling my mailbox
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 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 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 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 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 >>
Re: Dependabot emails are filling my mailbox
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 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 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 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 >
Re: Dependabot emails are filling my mailbox
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 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 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
Re: Dependabot emails are filling my mailbox
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 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
Re: Dependabot emails are filling my mailbox
I haven't tried it, but if you go to your settings for Github you can set dependabot to not notify you. That doesn't affect the notifications@ list of course. -Robert Middleton On Fri, Sep 23, 2022 at 7:47 PM Matt Sicker 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
Dependabot emails are filling my mailbox
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
