Group Pull requests based on the team name in a configuration file

[Mukhi09]

How are you running Renovate?

Self-hosted Renovate

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 problem

I have a monorepo containing multiple components, and each component has several environments — each with its own Helm chart and configuration file. Example folder structure

Comp-a/
|── dev/
│ ├── chart/Chart.yaml
│ ├── config.yaml
│
|── Rel/
├── chart/Chart.yaml
└── config.yaml

Comp-b/
|── dev/
│ ├── chart/Chart.yaml
│ └── config.yaml
|── Rel/
├── chart/Chart.yaml
└── config.yaml

Comp-C/
|── dev/
│ ├── chart/Chart.yaml
│ └── config.yaml
|── Rel/
├── chart/Chart.yaml
└── config.yaml

Contents of config.yaml looks like this

teamName:
clusterName:

A single team can own multiple components. I’d like to group pull requests based on the team name defined in the configuration file. For example, Comp-a, Comp-c is owned by same team. Now, Pull requests must be grouped per team.

Expected Outcome
PR1 -> Should contain changes of Comp-a and Comp-c
PR2 -> Should contain changes of Comp-b

Is this currently supported? I tried using additionalBranchPrefix with replace handlers, which groups PRs by component, but not by team.

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[RahulGautamSingh]

No, only grouping by filename using matchFileNames is possible at the moment.

[Mukhi09]

Hello,

Apologies for the late reply. Thank you for confirming.
Can we expect this feature as part of any future releases ?

[RahulGautamSingh]

I don't think it is currently required by most of renovate users. So, not likely