BOFH666, 1 year ago

Still testing and fiddling, but I’m using the forgejo-runner. Renovate is just another repository, with a workflow to get it started:

<span style="color:#323232;">on:
</span><span style="color:#323232;">  schedule:
</span><span style="color:#323232;">    - cron: '5 2 * * *'
</span><span style="color:#323232;">    - cron: '5 14 * * *'
</span><span style="color:#323232;">
</span><span style="color:#323232;">jobs:
</span><span style="color:#323232;">  build:
</span><span style="color:#323232;">    runs-on: docker
</span><span style="color:#323232;">    container:
</span><span style="color:#323232;">      image: renovate/renovate:37.140-full
</span><span style="color:#323232;">    steps:
</span><span style="color:#323232;">      - name: Checkout
</span><span style="color:#323232;">        uses: actions/checkout@v3
</span><span style="color:#323232;">
</span><span style="color:#323232;">      - name: Run renovate
</span><span style="color:#323232;">        env:
</span><span style="color:#323232;">          PAT: ${{ secrets.PAT }}
</span><span style="color:#323232;">          GITHUB_COM_TOKEN: ${{ secrets.GITHUB }}
</span><span style="color:#323232;">        run: |
</span><span style="color:#323232;">          echo "Running renovate"
</span><span style="color:#323232;">          cd ${GITHUB_WORKSPACE}
</span><span style="color:#323232;">          renovate --token ${PAT}          
</span>

The renovate image has been pulled by hand and the forgejo-runner will happily start the image. Both PAT and GITHUB secrets are configured as ‘action secrets’ within the renovate repository.

Besides the workflow, the repository contains renovate.json and config.js, so renovate has the correct configuration.