🔧 Repository: Renovate Recommendations for Plugin Adopters

[awanlin]

📜 Description

It would be awesome if we had some documentation around Renovate recommendations for Plugin Adopters.

Just general initial recommendations and then any further tips from what we've seen work well.

Another thing would be to provide guidance on how to group the plugins. For example right now in the Backstage Demo site we have several of the plugins in place but when Renovate creates the PRs there is one for each individual package.

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

[kim-tsao]

From our experience, the downside with grouping renovate PRs according to their workspaces is that it will generate a lot of PRs that could tie up the performance of GH actions, especially if there are tests that re-run with every branch recalculation. We wound up quieting PR creation in order to manage the noise until we find a better solution.

Here is an example of how we group renovate PRs based on teams.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.