Added grouping to Dependabot config yaml #92
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds dependency grouping to the Dependabot configuration to consolidate related dependency updates into single pull requests. The changes also update the update interval from weekly to quarterly for all package ecosystems.
- Added grouping configuration for gradle (backend) and npm (frontend) dependencies, separating production and development dependencies into distinct groups
- Changed update interval from "weekly" to "quarterly" for all three package ecosystems (github-actions, gradle, npm)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
EmielBoss
force-pushed
the
dependabot-grouping
branch
from
e4b4e3a to
ff09a36
Compare
EmielBoss
force-pushed
the
dependabot-grouping
branch
from
ff09a36 to
1f0b46f
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
.github/dependabot.yml
Outdated
| applies-to: version-updates | ||
| applies-to: security-updates |
There was a problem hiding this comment.
The 'applies-to' key is duplicated in this group configuration. In YAML, duplicate keys are not allowed - only the last value will be used. According to Dependabot documentation, 'applies-to' should be a single key with a value, and if you need to specify both version-updates and security-updates, you should use a list format or choose one value. The valid options are: "version-updates" or "security-updates". If you want the group to apply to both, you may need to check the current Dependabot documentation for the correct syntax, as the behavior may vary by version.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| groups: | ||
| dependencies-backend-production: | ||
| dependency-type: "production" | ||
| patterns: ["*"] | ||
| dependencies-backend-development: | ||
| dependency-type: "development" | ||
| patterns: ["*"] |
There was a problem hiding this comment.
The wildcard pattern "*" combined with dependency-type filtering will match all dependencies of that type. However, this creates two separate groups that will result in two separate pull requests (one for production dependencies and one for development dependencies). If the intention is to group all dependencies together in a single PR, consider removing the dependency-type filter and using a single group per ecosystem instead.
No description provided.