> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.6/devops-platform-integration/github-integration/setting-up-at-global-level/setting-parameters-for-github-actions.md).

# Setting parameters for GitHub Actions

Defining global-level parameters used in GitHub Actions workflows to connect to SonarQube Server 2025.6.

You can define at the global level the parameters used in GitHub Actions workflows to connect to the SonarQube Server (Server URL and token).

## Storing the authentication token in GitHub at the global level <a href="#token" id="token"></a>

To store sensitive data, use GitHub secrets: see GitHub’s documentation on [Encrypted secrets](https://docs.github.com/en/actions/reference/encrypted-secrets) for more information.

{% hint style="warning" %}
A token defined at the global level gives permissions on all projects in the SonarQube Server instance.
{% endhint %}

Proceed as follows to store the authentication token at the global level:

1. In the SonarQube Server UI, generate a SonarQube Server token at the global level.
2. Create an organization secret in GitHub with:
   * Name: SONAR\_TOKEN
   * Value: the token you generated in the previous step.

## Storing the SonarQube Server URL in GitHub at the global level <a href="#server-url" id="server-url"></a>

Create an [organization variable](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables) in GitHub with:

* Name: SONAR\_HOST\_URL
* Value: SonarQube Server URL.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.6/devops-platform-integration/github-integration/setting-up-at-global-level/setting-parameters-for-github-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.