-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dependabot #2025
base: main
Are you sure you want to change the base?
Add dependabot #2025
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Honestly, I don't see a need for it. I always find dependabots warnings to be annoying and not useful. Also, this module has no dependencies (aside from some utilities for testing), and we aim to keep it this way. I'm against. |
-1 on dependabot too. It pollutes search results with irrelevant hits, and mailbox with too much noise. |
If spam is a concern, we can limit the number of PRs it's opening. It also ensures that the github workflows are using their latest actions, which I think is a benefit to ensure that the work flow stays working and eventually saves you from spending time on upgrading it yourselves. |
We don't have many GitHub Actions workflow files, and we only use first-party actions from GitHub, and as of now, they're all on the latest version. Thank you for this PR and I appreciate enthusiasm, but I'm still against (just my opinion. I'm curious what other maintainers think). |
What type of PR is this?
What this PR does / why we need it:
Adds a dependabot configuration for automated dependency and github workflow updates.
Which issue(s) this PR fixes:
None, let me know if I need to create one first.