From 29dc953fa9c3534a7f2574ebb92caa448c473ce7 Mon Sep 17 00:00:00 2001 From: guillaume-peoch-sonarsource <91735163+guillaume-peoch-sonarsource@users.noreply.github.com> Date: Mon, 26 Sep 2022 14:21:00 +0200 Subject: [PATCH] Update README.md Co-authored-by: Duarte Meneses --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2a04a15..a456f22 100644 --- a/README.md +++ b/README.md @@ -102,7 +102,7 @@ More information about possible analysis parameters can be found in [the documen - `SONAR_TOKEN` – **Required** this is the token used to authenticate access to SonarQube. You can read more about security tokens [here](https://docs.sonarqube.org/latest/user-guide/user-token/). You can set the `SONAR_TOKEN` environment variable in the "Secrets" settings page of your repository, or you can add them at the level of your GitHub organization (recommended). - `SONAR_HOST_URL` – **Required** this tells the scanner where SonarQube is hosted. You can set the `SONAR_HOST_URL` environment variable in the "Secrets" settings page of your repository, or you can add them at the level of your GitHub organization (recommended). -- `SONAR_ROOT_CERT` – This is used to pass the scanner a custom root certificate (in PEM format), that should be used for validating the sonarqube server certificate. You can set the `SONAR_ROOT_CERT` environment variable in the "Secrets" settings page of your repository, or you can add them at the level of your GitHub organization (recommended). +- `SONAR_ROOT_CERT` – Holds an additional root certificate (in PEM format) that is used to validate the SonarQube server certificate. You can set the `SONAR_ROOT_CERT` environment variable in the "Secrets" settings page of your repository, or you can add them at the level of your GitHub organization (recommended). ## Alternatives for Java, .NET, and C/C++ projects