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
I have two Node projects in single repo with dependabot configured to update both. It is configured using the groups parameter to minimize the number of PRs created.
This working, so if a module common to both projects is update I get two PRs e.g.
PR1 - Update Module 1.1.1 > 1.1.2 (in /Extensions/BuildUpdating/BuildRetensionTask)
PR 2- Update Module 1.1.1 > 1.1.2 (in /Extensions/BuildUpdating/BuildVariableTask)
I need to deploy both these projects via a single CI/CD workflow, so it would be useful to group the dependabot updates both within each application and across the two package-ecosystem i.e. just getting a single PR that updates two eco systems
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
-
I have two Node projects in single repo with dependabot configured to update both. It is configured using the
groups
parameter to minimize the number of PRs created.This working, so if a module common to both projects is update I get two PRs e.g.
I need to deploy both these projects via a single CI/CD workflow, so it would be useful to group the dependabot updates both within each application and across the two
package-ecosystem
i.e. just getting a single PR that updates two eco systemsIs this currently possible or on the roadmap?
Beta Was this translation helpful? Give feedback.
All reactions