chore: don't create separate renovate PRs for angular and angular-cli

Author: pieh

renovate.json5

@@ -2,9 +2,12 @@
   $schema: 'https://docs.renovatebot.com/renovate-schema.json',
   extends: ['github>netlify/renovate-config:default'],
   ignorePresets: [':prHourlyLimit2'],
+  prHourlyLimit: 0,
   semanticCommits: true,
   // The config we're extending ignores test dirs, but we want to bump some fixture deps
   ignorePaths: ['**/node_modules/**'],
+  // We creating our own package rule that bundles those two together, so let's avoid separate ones
+  ignorePresets: ['monorepo:angular', 'monorepo:angular-cli'],
   packageRules: [
     // Since we've enabled Renovate (see above) for fixture sites, adjust the config for these.
     {
@@ -16,9 +19,11 @@
     },
     {
       description: 'Stable & unstable Angular bumps in test fixtures',
+      groupName: 'Angular packages',
       matchFileNames: ['tests/**/fixtures/**/package.json'],
-      // See https://docs.renovatebot.com/presets-monorepo/#monorepoangular.
-      matchSourceUrls: ['https://github.com/angular/angular'],
+      // See https://docs.renovatebot.com/presets-monorepo/#monorepoangular and https://docs.renovatebot.com/presets-monorepo/#monorepoangular-cli.
+      // packages from both monorepos should be bumped together
+      matchSourceUrls: ['https://github.com/angular/angular', 'https://github.com/angular/angular-cli'],
       // Override the schedule to get immediate PRs.
       schedule: null,
       // Apply a unique label so we can trigger additional workflows for these PRs.