Live data from Hacker News

Reducing Dependabot Noise

nesbitt.io

41–50 of 50 posts

Re: Reducing Dependabot Noise

#46

Take a look at pr-bot: https://github.com/marqeta/pr-bot The answer to dependabot, or snyk prs is to automatically merge them once all the status checks pass. This free your devs from having to worry about patching. PR-BOT will let you define policy on when it’s ok to automerge prs.

I don’t have experience with dependabot at all. I didn’t realize it was satire. I just kept thinking, “This sounds like terrible advice. This can’t be right.”

Re: Reducing Dependabot Noise

#47
post #42

I gotta admit you had me thinking this was serious until the `Remove lockfiles` section ;)

Not "you can always rewrite it yourself in Rust over a weekend"?

"If it has been mass maintained by some random person in Nebraska since 2003, that is battle-tested infrastructure." comes before that.

Re: Reducing Dependabot Noise

#48
post #46

Take a look at pr-bot: https://github.com/marqeta/pr-bot The answer to dependabot, or snyk prs is to automatically merge them once all the status checks pass. This free your devs from having to worry about patching. PR-BOT will let you define policy on when it’s ok to automerge prs.

I don’t have experience with dependabot at all. I didn’t realize it was satire. I just kept thinking, “This sounds like terrible advice. This can’t be right.”

This is not satire.

If you have a large dependency graph, you are going to have a lot of vulnerable stuff.

Letting one computer send you patches and the other computer merge it for you when all your tests pass is a good thing.

Re: Reducing Dependabot Noise

#49
post #41

In this thread we get to see which usernames display an inability to detect very obvious satire.

It got me until "Remove lockfiles from version control"

My favorite was

If it has been mass maintained by some random person in Nebraska since 2003, that is battle-tested infrastructure.

Post reply on HN