This repository was archived by the owner on Aug 2, 2022. It is now read-only.
Removing NPM ecosystem from dependabot settings file#917
Merged
Conversation
venu-block1
approved these changes
Apr 23, 2021
938a319 to
d7f2bcb
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Change Description
Unfortunately Github's built-in dependabot is missing two crucial features that would allow easier use: Grouping of PRs instead of separate PRs per dependency, and filtering updates to specific types.
Filtering updates was available in the old dependabot which still has documentation that unfortunately isn't correct for Github's built-in version. This would be fine if it was also possible to group weekly dependency updates into one PR, but unfortunately without these two features, dependabot will open too many PRs too frequently.
The CI/CD workflow has a task that updates all dependencies, as long as commits/PRs are actively being created, this will suffice until dependabot gets more features. Additionally, security updates will need to stay open against master (until a release solves the security issue) and cloned into develop and release branches.
API Changes
Documentation Additions