Skip to content

Commit f2d401e

Browse files
committed
Remove section about CR_TOKEN from README
Signed-off-by: Stuart P. Bentley <[email protected]>
1 parent c1a55c4 commit f2d401e

1 file changed

Lines changed: 0 additions & 5 deletions

File tree

README.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,6 @@ A GitHub action to turn a GitHub project into a self-hosted Helm chart repo, usi
77
### Pre-requisites
88

99
1. A GitHub repo containing a directory with your Helm charts (eg: `/charts`)
10-
1. A GitHub project [Secret](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets#creating-encrypted-secrets) named `CR_TOKEN` with the value of a GitHub [personal access token](https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line#creating-a-token)
11-
* The token must have `repo` scope
12-
* The token's user must have write access to the project
13-
* To mitigate risk you may wish to limit the token to a single project by creating a [machine user](https://developer.github.com/v3/guides/managing-deploy-keys/#machine-users)
14-
* Please note the personal access token is required because of an [Actions bug](https://github.community/t5/GitHub-Actions/Github-action-not-triggering-gh-pages-upon-push/m-p/31266/highlight/true#M743), and will hopefully be unnecessary in the future
1510
1. Create a workflow `.yml` file in your `.github/workflows` directory. An [example workflow](#example-workflow) is available below.
1611
For more information, reference the GitHub Help Documentation for [Creating a workflow file](https://help.github.com/en/articles/configuring-a-workflow#creating-a-workflow-file)
1712

0 commit comments

Comments
 (0)