Support settings for groups in repositories list on self hosted

[erpel]

Tell us more.

We're running a self hosted renovate for repositories from a few different teams. For convenience we'd like to provide some settings based on the main config.

It would be great to be able to set things like for multiple repositories. Right now it works for one or all.
As an example, if I want to specify a certain commitMessagePrefix for some but not all repos, it requires a good bit of repetition:

 commitMessagePrefix: "[Renovate]",
 repositories: [
   {
     repository: 'teamA/repoOne',
     commitMessagePrefix: "[bot]"
   },
   {
     repository: 'teamA/repoOne',
     commitMessagePrefix: "[bot]"
   },
   'teamB/alpha',
   'teamB/alpha',
   'teamB/alpha'
 ],

It would be lovely if something like this could be made to work:

commitMessagePrefix: "[Renovate]",
repositories: [ 
 {
   commitMessagePrefix: "[bot]",
   repositories: [ 
     'teamA/repoOne',
     'teamA/repoOne'
   ]
},
'teamB/alpha',
'teamB/alpha',
'teamB/alpha'
],

[gaeljw]

Can't you use presets?

You can define at several levels. For instance we have a bunch of configs for the entire company in one preset, then each team (= GitLab group) inherits it and may add some specific ties, finally each repo inherits the team's preset and can also add some customisation.

[erpel]

I thought about this, but in this case I'm looking at
a) some settings things that are specific to the admin/bot config like allowedCommands.
b) trying to provide a fully managed experience.

I do concede that by including a self hosted preset in the onboarding config, I can take care of most of the "convenience" part of this related to settings that can be configured on a repository level.