Skip to content

Update Sonar token reference in build workflow - #17

Open
damesx04 wants to merge 1 commit into
sonarsource-cfamily-examples:mainfrom
damesx04:main
Open

Update Sonar token reference in build workflow#17
damesx04 wants to merge 1 commit into
sonarsource-cfamily-examples:mainfrom
damesx04:main

Conversation

@damesx04

@damesx04 damesx04 commented Dec 5, 2025

Copy link
Copy Markdown

No description provided.

Copilot AI review requested due to automatic review settings December 5, 2025 20:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Sonar token secret reference in the GitHub Actions build workflow from SONARCLOUD_TOKEN to SONAR_TOKEN.

Key Changes

  • Modified the environment variable reference in the SonarQube scan step to use a different GitHub secret name

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

uses: SonarSource/sonarqube-scan-action@v4
env:
SONAR_TOKEN: ${{ secrets.SONARCLOUD_TOKEN }} # Put the name of your token here
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Put the name of your token here

Copilot AI Dec 5, 2025

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The secret name is being changed from SONARCLOUD_TOKEN to SONAR_TOKEN, but the configuration in sonar-project.properties indicates this is a SonarCloud setup (contains sonar.organization which is SonarCloud-specific). While the sonarqube-scan-action accepts SONAR_TOKEN as the environment variable name for both SonarQube and SonarCloud, the original name SONARCLOUD_TOKEN was more descriptive for this SonarCloud setup.

Consider:

  1. If this is intentional to standardize on SONAR_TOKEN, ensure the GitHub secret is renamed from SONARCLOUD_TOKEN to SONAR_TOKEN in the repository settings, or
  2. Keep using SONARCLOUD_TOKEN for clarity since this is a SonarCloud setup, not a self-hosted SonarQube instance.
Suggested change
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Put the name of your token here
SONARCLOUD_TOKEN: ${{ secrets.SONARCLOUD_TOKEN }} # Put the name of your SonarCloud token here

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants