GitHub Action to run Renovate self-hosted.

• Badges
• Options
  • configurationFile
  • token
• Example
• License

Badge	Description	Service
	Code style	Prettier
	Commit style	Conventional Commits
	Dependencies	Renovate
	Lint commit messages	GitHub Actions
	Lint	GitHub Actions
	Example	GitHub Actions

Configuration file to configure Renovate. The configurations that can be done in this file consists of two parts, as listed below. Refer to the links to the Renovate Docs for all options and see the example/config.js for an example configuration.

1. Self-Hosted Configuration Options
2. Configuration Options

The branchPrefix option is important to configure and should be configured to a value other than the default to prevent interference with e.g. the Renovate GitHub App.

Generate a personal access token, with public_repo rights for only public repositories or repo rights for public and private repositories, and add it to Secrets (repository settings) as RENOVATE_TOKEN. This token is only used by Renovate, see the token configuration, and gives it access to the repositories. The name of the secret can be anything as long as it matches the argument given to the token option.

Note that the GITHUB_TOKEN secret can't be used for authenticating Renovate.

This example uses a personal access token that is a GitHub secret named RENOVATE_TOKEN.

name: Example
on: push
jobs:
  example:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Self-hosted Renovate example
        uses: vidavidorra/[email protected]
        with:
          configurationFile: example/config.js
          token: ${{ secrets.RENOVATE_TOKEN }}

This project is licensed under the GPLv3 license.

Copyright © 2020 Jeroen de Bruijn