-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.github: switch to using renovate batched update prs #747
Conversation
does it work for action updates, too? if so, I love this! |
answering my own question: yes it does |
This is a suggestion to improve dependency upgrade PRs for bubbletea. The provided renovate.json configuration batches updates into a single PR that the bot keeps up to date with the latest versions of deps. This helps to prevent pull request spam from dependabot + PR fatigue. Signed-off-by: Christian Stewart <[email protected]>
e4cc9ab
to
232d24c
Compare
i think we can close this tbh, we're already using dependabot everywhere... |
Just wanted to say appreciate the PR (as always) @paralin. In this case we're sticking with our existing tooling because of the degree in which it's woven into our workflows. |
That's fine, it was just a suggestion. That said, I still think the advantages to batched PRs are there. |
It's a fair point; will definitely keep it mind when we take a breath and reexamine our tooling. |
This is a suggestion to improve dependency upgrade PRs for bubbletea.
The provided renovate.json configuration batches updates into a single PR that the bot keeps up to date with the latest versions of deps.
This helps to prevent pull request spam from dependabot + PR fatigue.
Here's an example of what an upgrade PR looks like: aperturerobotics/controllerbus#104
Also keeps the github workflow steps up to date.