Skip to content

Using GITHUB_TOKEN should be possible now #842

Closed

Description

@TheMeier

For me using this worked:

jobs:
  renovate:
    permissions:
      contents: read
      issues: read
      pull-requests: write
      repository-projects: read
      statuses: read
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4.1.6
      - name: Renovate
        uses: renovatebot/github-action@v40.1.11
        with:
          configurationFile: renovate-config.json
          token: ${{ secrets.GITHUB_TOKEN }}

Note the permissions section. Maybe that is related to #796

Activity

  1. locked and limited conversation to collaborators on Jun 5, 2024
  2. converted this issue into a discussion #843 on Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Datasource

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions