From 6807ad999e1a1e244a5a97ea9f93514aa4f499df Mon Sep 17 00:00:00 2001 From: FineFindus <63370021+FineFindus@users.noreply.github.com> Date: Tue, 18 Jul 2023 14:59:29 +0200 Subject: [PATCH] docs(deploy-gh-pages): add workflow permissions (#2249) --- docs/content/documentation/deployment/github-pages.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/content/documentation/deployment/github-pages.md b/docs/content/documentation/deployment/github-pages.md index ded7a8a734..16d4c30a3f 100644 --- a/docs/content/documentation/deployment/github-pages.md +++ b/docs/content/documentation/deployment/github-pages.md @@ -35,6 +35,7 @@ Let's start with the token. Remember, if you are publishing the site on the same For creating the token either click on [here](https://github.com/settings/tokens/new?scopes=public_repo) or go to Settings > Developer Settings > Personal access tokens. Under the *Select Scopes* section, give it *public_repo* permissions and click *Generate token*. Then copy the token, navigate to your repository and add in the Settings tab the *Secret* `TOKEN` and paste your token in it. Next we need to create the *Github Action*. Here we can make use of the [zola-deploy-action](https://github.com/shalzz/zola-deploy-action). Go to the *Actions* tab of your repository, click on *set up a workflow yourself* to get a blank workflow file. Copy the following script into it and commit it afterwards; note that you may need to change the `github.ref` branch from `main` to `master` or similar, as the action will only run for the branch you choose. +If you get a permissions denied error, you may need to change the workflow permissions to read and write in Settings > Actions > Workflow permissions. ```yaml # On every push this script is executed