Skip to content

Conversation

@froblesmartin
Copy link
Contributor

Fixes #898

[Generate a Personal Access Token (classic)](https://github.com/settings/tokens), with the `repo:public_repo` scope for only public repositories or the `repo` scope for public and private repositories, and add it to _Secrets_ (repository settings) as `RENOVATE_TOKEN`.
[Generate a GitHub Personal Access Token (fine-grained is recommended)](https://github.com/settings/tokens) (see the [GitHub authentication docs](https://docs.renovatebot.com/modules/platform/github/#authentication)) and add it to _Secrets_ (repository settings) as `RENOVATE_TOKEN`.
You can also create a token without a specific scope, which gives read-only access to public repositories, for testing.
This token is only used by Renovate, see the [token configuration](https://docs.renovatebot.com/self-hosted-configuration/#token), and gives it access to the repositories.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@viceice let me know if this line is really useful, AFAIK it doesn't really explain anything 🤷

The name of the secret can be anything as long as it matches the argument given to the `token` option.

Note that Renovate _cannot_ currently use [Fine-grained Personal Access Tokens](https://github.com/settings/tokens?type=beta) since they do not support the GitHub GraphQL API, yet.
The secret's name can be anything if it matches the argument given to the `token` option.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That line was there before 🤷 .

My understanding of it is that, when using this GitHub Action, you can call the GitHub Secret however you want, as long as you pass it to the token input. E.g.:

      - name: Self-hosted Renovate
        uses: renovatebot/[email protected]
        with:
          docker-user: root
          token: ${{ secrets.MY_SUPER_RENOVATE_TOKEN_WITH_MY_OWN_NAME_YAY }}

Copy link
Member

@viceice viceice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fine grained pat doesn't has access to checks API, so it's pretty useless to renovate

@froblesmartin
Copy link
Contributor Author

fine grained pat doesn't has access to checks API, so it's pretty useless to renovate

Why is that required always? Using it to open PRs with the updates, at least without auto-merge, it does not need to use the Checks API AFAIK 🤔

@viceice
Copy link
Member

viceice commented Sep 11, 2025

fine grained pat doesn't has access to checks API, so it's pretty useless to renovate

Why is that required always? Using it to open PRs with the updates, at least without auto-merge, it does not need to use the Checks API AFAIK 🤔

Then please add a note, that automerge isn't possible with those PAT's. Otherwise users would expect those PAT's are a full drop-in replacement

@viceice viceice removed the request for review from rarkins September 11, 2025 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: fine grained PAT's are now supported

3 participants