Automatically group packages by sourceUrl

[mmkal]

Tell us more.

matchSourceUrls can be used to group packages from specific github repos, but it'd be great for there to be an option something like this

{
  "groupBySourceUrl": "repository"
}

The way I could imagine this working is if two packages specify the same github repo, but are not included in the very-long-but-never-exhaustive list of known monorepos, renovate would still know to group them together (using a slug based on the github organization+repo). For example I just noticed one of my repos had separate updates for @orpc/server and @orpc/contract - I imagine it's exhausting for the renovate team to try to keep up with all the "popular" monorepos that continually sprout up. This would catch pretty much all of them, including future ones, in one go.

[astellingwerf]

matchSourceUrls has support for regex and glob matching patterns.

[mmkal]

I'm not sure that helps, unless I can use regex capture groups in the group name/slug, can I do that? Otherwise wouldn't it just group everything together?

[astellingwerf]

In that case I'm not sure what you're asking. I thought you are just looking for a package rule like:

{
  "packageRules": [
    {
      "matchSourceUrls": ["/https:\/\/github.com\/unnoq\/.*/"],
      "groupName": "unnoq"
    }
  ]
}

[mmkal]

I want renovate to smartly group things so that it groups unnoq/orpc packages automatically, without me having to remember to add anything to the config that's specifically about unnoq or orpc. orpc was just an example of a monorepo that the renovate team hadn't explicitly listed yet as a "known monorepo". I'd like to write this imaginary config (I think taking advantage of existing regex matching seems sensible):

{
  "packageRules": [
    {
      "matchSourceUrls": ["/https:\/\/github.com\/(.+?)\/(.+?)/"],
      "groupName": "$1-$2"
    }
  ]
}

And for that to be enough for renovate to match the source url https://github.com/unnoq/orpc against a bunch of different packages, and match the regex to get capture group 1 = unnoq, capture group 2 = orpc. So all of the orpc packages end up with groupName = unnoq-orpc.

This would be generalizable, and cover everybody's configs without the renovate team, or individual users, having to list every monorepo in existence.

[rarkins]

I found the old Issue where I'd discussed something similar. In particular, please see #7737 (comment)

I agree with the idea of grouping by source repo by default, although potentially retaining backwards compatibility for existing users so that the millions of open Renovate PRs in the world don't all get closed and recreated with a new branch name overnight

[kachkaev]

👋 @mmkal! I know that this does not fully solve your issue, but I've added ORPC to the know list of monrepos in #41115.