From 23af360ef00ebf4ff43ce25868981d3678b70af7 Mon Sep 17 00:00:00 2001 From: Maik Riechert Date: Thu, 16 Dec 2021 14:54:55 +0100 Subject: [PATCH] Remove text on GITHUB_TOKEN which is now built-in (#8907) Merge pull request 8907 --- .../continuous-integration/github-actions.md | 19 ++----------------- 1 file changed, 2 insertions(+), 17 deletions(-) diff --git a/docs/_docs/continuous-integration/github-actions.md b/docs/_docs/continuous-integration/github-actions.md index 1dfd41d0..ade090ee 100644 --- a/docs/_docs/continuous-integration/github-actions.md +++ b/docs/_docs/continuous-integration/github-actions.md @@ -129,7 +129,8 @@ The above workflow can be explained as the following: - We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`. This handles the build and deploy. - We set a reference to a secret **environment variable** for the action to use. The `GITHUB_TOKEN` - is a _Personal Access Token_ and is detailed in the next section. + is a secret token automatically initialized at the start of every workflow run. + More information can be found in [GitHub documentation](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret). Instead of using the **on.push** condition, you could trigger your build on a **schedule** by using the [on.schedule] parameter. For example, here we build daily at midnight by specifying @@ -146,22 +147,6 @@ Note that this string must be quoted to prevent the asterisks from being evaluat [on.schedule]: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule [crontab guru]: https://crontab.guru/ -### Providing permissions - -The action needs permissions to push to your `gh-pages` branch. So you need to create a GitHub -**authentication token** on your GitHub profile, then set it as an environment variable in your -build using _Secrets_: - -1. On your GitHub profile, under **Developer Settings**, go to the [Personal Access Tokens][tokens] - section. -2. **Create** a token. Give it a name like "GitHub Actions" and ensure it has permissions to - `public_repos` (or the entire `repo` scope for private repository) --- necessary for the action - to commit to the `gh-pages` branch. -3. **Copy** the token value. -4. Go to your repository's **Settings** and then the **Secrets** tab. -5. **Create** a token named `GITHUB_TOKEN` (_important_). Give it a value using the value copied - above. - ### Build and deploy On pushing any local changes onto `main`, the action will be triggered and the build will