-
Notifications
You must be signed in to change notification settings - Fork 26
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
ci: Remove RenovateBot #329
Conversation
We'd prefer to use Github's integrated Dependabot for version upodates and security updates, as that's more widely used for open source software. Adding Dependabot's version updating capabilities is done in a separate PR.
There's a separate PR #329 to remove Renovate, so that we don't get duplicate dependency upgrade PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Since renovate is not running as a GitHub Action / Workflow, I think it might be installed as an app. If that's the case, I am not sure if removing the config will completely disable the bot, or if it will fall back to a default config then. If it's enabled orga-wide we could disable it here with @patrick246 could you check, if renovate is installed as an app? |
Updated the PR, so that the CI doesn't fail on semgrep. PS: We also need to close all RenovateBot PRs after this is merged, so that Dependabot can take over from here. |
Yes, renovate was installed as an App, I have revoked permissions on this repository |
There's a separate PR #329 to remove Renovate, so that we don't get duplicate dependency upgrade PRs. Co-authored-by: Marvin Wendt <[email protected]>
We'd prefer to use Github's integrated Dependabot for version upodates and security updates, as that's more widely used for open source software.
Adding Dependabot's version updating capabilities is done in a separate PR.
Part of #312.