groupName doesnt group if existing PR is open #31762
-
What would you like help with?I think I found a bug How are you running Renovate?Self-hosted If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.Github Please tell us more about your question or problemWhen using I believe this occurs because the groupName has no dynamic value and therefore if it already exists it cannot create a new PR with the same groupname. Ideally if the PR is still open, on the next run future pkgs will get aggregated into the same PR or we should be able to add a dynamic unique identifier so pkgs are also always aggregated but will go in separate PRs if they are raised at different times. This issue was seen when a groupName'd PR was already raised, and in the renovate dashboard the rate limited PRs that should fall under the groupName wanted to be created as separate PRs. Logs (if relevant)An example from renovate dashboard (fields replaced) where
All of these fall under the group since they are all |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi there, A maintainer decided this is not a bug, and behaving as designed. The maintainer will explain why this behavior is correct. To avoid confusing future readers, we will close this Discussion. We want Bug-type Discussions to be about things that we rate as bugs. For more details, please read our development docs about bug handling. If this bug report makes you think of an idea for a new feature, or how to improve a current feature, feel free to create a new Suggest an Idea Discussion. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
Your glob pattern doesn't match the
/
. Test out your patterns on https://www.digitalocean.com/community/tools/glob