From c3b609966b18b96e4a7f7686ff64f0df84ebdd03 Mon Sep 17 00:00:00 2001
From: Alix Lourme <alix.lourme@gmail.com>
Date: Thu, 28 Nov 2019 14:58:03 +0100
Subject: [PATCH] Clarifications about YAML snippet and GITHUB_TOKEN

---
 README.md | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 6e0d0b9..09e5664 100644
--- a/README.md
+++ b/README.md
@@ -24,14 +24,6 @@ sonar.projectKey=<replace with the key generated when setting up the project on
 sonar.sources=.
 ```
 
-You can change the analysis base directory by using the optional input `projectBaseDir` like this:
-
-```yaml
-uses: sonarsource/sonarcloud-github-action@master
-with:
-  projectBaseDir: my-custom-directory
-```
-
 The workflow, usually declared in `.github/workflows/build.yml`, looks like:
 
 ```yaml
@@ -50,9 +42,18 @@ jobs:
         SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
 ```
 
+You can change the analysis base directory by using the optional input `projectBaseDir` like this:
+
+```yaml
+uses: sonarsource/sonarcloud-github-action@master
+with:
+  projectBaseDir: my-custom-directory
+```
+
 ### Secrets
 
 - `SONAR_TOKEN` – **Required** this is the token used to authenticate access to SonarCloud. You can generate a token on your [Security page in SonarCloud](https://sonarcloud.io/account/security/). You can set the `SONAR_TOKEN` environment variable in the "Secrets" settings page of your repository.
+- *`GITHUB_TOKEN` – Provided by Github (see [Authenticating with the GITHUB_TOKEN](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)).*
 
 ## Example of pull request analysis