From c27ab213c7fde35645f5079ddcac44c0bcee10c3 Mon Sep 17 00:00:00 2001 From: Godfrey Chan Date: Thu, 2 Apr 2020 13:38:43 -0700 Subject: [PATCH 1/2] Provide default for GITHUB_TOKEN See https://github.com/actions/checkout/blob/94c2de77cccf605d74201a8aec6dd8fc0717ad66/action.yml#L24 --- action.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/action.yml b/action.yml index 1e93f60..d7b9e3d 100644 --- a/action.yml +++ b/action.yml @@ -11,6 +11,7 @@ inputs: GITHUB_TOKEN: description: 'Access token for the repository, available under the same name in secrets.' required: true + default: ${{ github.token }} skip-tags: description: 'true/false. If enabled, tag build artifacts (e.g. release artifacts) will be kept.' required: false From 6a22147dd93039514966f618fb3e85f15d63c729 Mon Sep 17 00:00:00 2001 From: Godfrey Chan Date: Fri, 3 Apr 2020 11:09:34 -0700 Subject: [PATCH 2/2] Remove token from README Since it is set by default, it should be rare to have to customize it. --- README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/README.md b/README.md index 7a96d2f..6237bac 100644 --- a/README.md +++ b/README.md @@ -39,11 +39,9 @@ jobs: - name: Remove old artifacts uses: c-hive/gha-remove-artifacts@v1 with: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} age: '1 month' skip-tags: true ``` -_Note: `secrets.GITHUB_TOKEN` is a repository-level access token already provided by the Actions framework, you don't need to set any secrets._ ## Conventions