Create grouped dependabot.yml #843
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #840 I know @sindresorhus thinks this can get noisy, but I tried to make it as non-noisy as possible. I would really love to get notified when eg. a new `tsd`, `xo` or similar dependency needs to be updated, and same for GitHub Actions. This setup makes it so that at max one PR for npm and one PR for GitHub Actions will be created, and it will only be created/updated weekly, and for npm it will only create it if the version range _needs_ to be increased, so no needless bumping of the lower range of a version.
sindresorhus
approved these changes
Mar 22, 2024
|
I'm willing to try it out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #840
I know @sindresorhus thinks this can get noisy, but I tried to make it as non-noisy as possible.
I would really love to get notified when eg. a new
tsd,xoor similar dependency needs to be updated, and same for GitHub Actions.This setup makes it so that at max one PR for npm and one PR for GitHub Actions will be created, and it will only be created/updated weekly, and for npm it will only create it if the version range needs to be increased, so no needless bumping of the lower range of a version.
Can we give this a test and revisit it in a couple of weeks and see if it did get too noisy?