chore(renovate): update config to create team specific PRs #1637
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: https://issues.redhat.com/browse/RHIDP-2190
team/<plugin-team>
labels added for grouped PR except for Vulnerability alerts. TheadditionalBranchPrefix
was creating multiple dup PRs (based on unique branch names). I had to reset this value to "" in the VulnerabilityAlerts rule in order to fix this, which means we can't label this. We will rely on CODEOWNERS to assign to the right team in this case. Since most security vulns affect the root yarn.lock file, they should be correctly assigned to themaintainers-plugins
team (from CODEOWNERS file)See test repo for results:
Dashboard
PRs