Skip to content

Set explicit check-sca project key metadata#87

Merged
lijun-chen-sonarsource merged 1 commit into
masterfrom
mm/fix-check-sca
May 20, 2026
Merged

Set explicit check-sca project key metadata#87
lijun-chen-sonarsource merged 1 commit into
masterfrom
mm/fix-check-sca

Conversation

@mostafa-mohammed-sonarsource
Copy link
Copy Markdown
Contributor

Summary

  • add .github/repo-metadata.yaml
  • set check-sca.project-key to org.sonarsource.sslr:sslr

Why

check-sca key auto-discovery can resolve to SonarSource_sslr, while the actual Sonar project key is org.sonarsource.sslr:sslr. Setting the project key explicitly makes the check query the correct project.

Reference

Add .github/repo-metadata.yaml with the explicit Sonar project key used by sslr.

This follows the ci-github-actions guidance for repositories where automatic key discovery can resolve to a non-matching key, so the check-sca action can query the intended project directly.
@sonar-review-alpha
Copy link
Copy Markdown

sonar-review-alpha Bot commented May 20, 2026

Summary

This PR adds a new .github/repo-metadata.yaml file that explicitly configures the SonarQube Cloud project key for the check-sca action. Without this explicit mapping, the check-sca auto-discovery was resolving to SonarSource_sslr instead of the correct Sonar project key org.sonarsource.sslr:sslr, causing checks to query the wrong project.

What reviewers should know

What to check:

  • Verify that org.sonarsource.sslr:sslr is the correct Sonar project key for this repository (confirm in SonarQube Cloud)
  • The new file is placed in the standard location (.github/) where GitHub Actions can find it

Context:

  • This is a single, minimal configuration file with no code changes
  • The change affects the check-sca GitHub Action behavior, which is typically triggered as part of CI/CD workflows
  • See the SonarSource ci-github-actions README linked in the description for how this file is used

  • Generate Walkthrough
  • Generate Diagram

🗣️ Give feedback

Copy link
Copy Markdown

@sonar-review-alpha sonar-review-alpha Bot left a comment

Choose a reason for hiding this comment

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

LGTM! ✅

Clean, minimal change — no issues found.

🗣️ Give feedback

@sonarqube-next
Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link
Copy Markdown

@lijun-chen-sonarsource lijun-chen-sonarsource left a comment

Choose a reason for hiding this comment

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

Thanks for taking care of this. LGTM!

@lijun-chen-sonarsource lijun-chen-sonarsource merged commit ffcf8f3 into master May 20, 2026
7 checks passed
@lijun-chen-sonarsource lijun-chen-sonarsource deleted the mm/fix-check-sca branch May 20, 2026 07:48
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