VictoriaMetrics / VictoriaMetrics/operator
renovate: tweak the configs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 589
- Forks
- 229
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 77
Description
We're running way too many Actions when Renovate creates a lot of PRs. Each merge causes each PR to be rebased automatically and run CI again.
Ideas:
- set cooldown / limit to renovate PR
- configure Renovate to bundle updates into one instead of creating 10+
- disable autorebase - we can do it when we're ready to merge
- disable automatic CI runs for Renovate PRs - we can allow running tests manually when the PR is ready to merge
I think the first one would be most useful - most of our dependencies are interconnected as k8s deps.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's Renovate configuration and GitHub Actions workflows, then determine which configuration controls PR cooldown or limits. The issue presents several alternatives rather than a fixed scope; done should mean one agreed approach reduces automatic rebases and CI runs for Renovate PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100