No description
01ea579aef
This patch changes the automerge config to use the gitlab native feature of automerging changing using the "merge if CI pipeline success" feature. This should prevent the current situation where automerge is enabled but not used due to the fact that renovate bots runs as cronjob instead of being the server-side application. |
||
---|---|---|
.gitlab-ci.yml | ||
config.js | ||
LICENSE | ||
README.md | ||
renovate.json |
Renovate Bot
This repository is a GitLab repository to run Renovate Bot in a self-hosted GitLab instance via GitLab CI. It provides basic features for dependency updates.
Usage
On the SI-GitLab instance authorize the user Botaniker to have access to your repository. The current schedule for this to run is once a week. You'll get a setup MR from Botaniker within a week. Once it's merged, it'll automatically check your dependencies and inform you about updates.
If you want to run this on your own GitLab instance:
- Clone this repository and set it up on your own GitLab instance.
- Create a user for the bot and create and API access token.
- Go to Settings -> CI/CD -> Variables of your
renovate bot
-repository. Add a variable calledRENOVATE_TOKEN
and fill it with the access token from step 2. - Setup a GitLab CI schedule for the
renovate bot
-repository to run on a regular basis. - Grant your bot user access to repositories you want to have checked.
More information
- Check the official renovate bot page.
- See the docs about how to tweak the renovate bot config files
- Feel free to report issues here