You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using the group support in dependabot.yml to try to group PRs by package ecosystem. We have many npm locations (e.g. for AWS lambdas) and want to keep dependencies in sync across all of them, so we don't ever want an update that only affects a single package.json.
Dependabot creates grouped PRs correctly, but for the npm package ecosystem using directories: it also creates an individual PR for every update. How can we prevent this? It doesn't happen for the gradle package ecosystem.
Note that these are not security updates, we have no security bulletins for these bumps.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
We're using the group support in
dependabot.yml
to try to group PRs by package ecosystem. We have many npm locations (e.g. for AWS lambdas) and want to keep dependencies in sync across all of them, so we don't ever want an update that only affects a singlepackage.json
.Dependabot creates grouped PRs correctly, but for the npm package ecosystem using
directories:
it also creates an individual PR for every update. How can we prevent this? It doesn't happen for the gradle package ecosystem.Note that these are not security updates, we have no security bulletins for these bumps.
Our
dependabot.yml
:Beta Was this translation helpful? Give feedback.
All reactions