From 85bfa952e48108dbdcfa49105d072b3170d08a0f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Orhun=20Parmaks=C4=B1z?= Date: Thu, 8 Aug 2024 10:57:00 +0300 Subject: [PATCH] docs(website): clarify authentication with GitHub token (#787) --- website/docs/integration/github.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/integration/github.md b/website/docs/integration/github.md index 98e40aa4e3..d71e992bc6 100644 --- a/website/docs/integration/github.md +++ b/website/docs/integration/github.md @@ -51,7 +51,7 @@ Although this is enough for a couple of runs of **git-cliff**, it is suggested t :::tip -Follow [this guide](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) for creating an access token. It can be either a classic or fine-grained token _without_ permissions. +Follow [this guide](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) for creating an access token. It can be either a classic or fine-grained token **without permissions**. Also, if you are running **git-cliff** in GitHub Actions, using `${{ secrets.GITHUB_TOKEN }}` is also enough. :::