From b65cf4a256957c995023f7957deb82a87775b142 Mon Sep 17 00:00:00 2001 From: Barry Date: Mon, 10 Aug 2020 23:38:53 +0100 Subject: [PATCH 1/2] More explanation of GITHUB_TOKEN --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index bd7857b1..c425ce46 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ To use this **GitHub** Action you will need to complete the following: 5. Enjoy your more _stable_, and _cleaner_ code base 6. Check out the [Wiki](https://github.com/github/super-linter/wiki) for customization options -**NOTE:** You will need the _Environment_ variable `GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}` set in your workflow file to be able to use the multiple status API returns. There is no need to set the **GitHub** Secret, it only needs to be passed. +**NOTE:** If you pass the _Environment_ variable `GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}` in your workflow file, then the GitHub Super-Linter will mark the status of each individual linter run in the Checks section of a pull request. There is no need to set the **GitHub** Secret as it is automatically set by GitHub, it only needs to be passed to the action. ### Example connecting GitHub Action Workflow From 44e48abb43ff171272c7d339fee1cd67a205c125 Mon Sep 17 00:00:00 2001 From: Barry Date: Mon, 10 Aug 2020 23:41:32 +0100 Subject: [PATCH 2/2] Bit more explanation --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c425ce46..167b6f37 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ To use this **GitHub** Action you will need to complete the following: 5. Enjoy your more _stable_, and _cleaner_ code base 6. Check out the [Wiki](https://github.com/github/super-linter/wiki) for customization options -**NOTE:** If you pass the _Environment_ variable `GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}` in your workflow file, then the GitHub Super-Linter will mark the status of each individual linter run in the Checks section of a pull request. There is no need to set the **GitHub** Secret as it is automatically set by GitHub, it only needs to be passed to the action. +**NOTE:** If you pass the _Environment_ variable `GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}` in your workflow, then the **GitHub Super-Linter** will mark the status of each individual linter run in the Checks section of a pull request. Without this you will only see the overall status of the full run. There is no need to set the **GitHub** Secret as it is automatically set by GitHub, it only needs to be passed to the action. ### Example connecting GitHub Action Workflow