CICD-12529: Add SONAR_SKIP condition to SonarQube scan#81
Merged
TimmersThomas merged 1 commit intomainfrom Apr 7, 2026
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
TimmersThomas
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CICD-12529: Add SONAR_SKIP condition to SonarQube scan
This PR adds an
if: vars.SONAR_SKIP != 'TRUE'condition to allsonarsource/sonarqube-scan-actionsteps in this repository's workflows.When the org-level variable
SONAR_SKIPis set toTRUE, the SonarQube scan step will be skipped. Otherwise it runs as normal.Files changed
.github/workflows/validate.ymlAutomated change by CICD-12529 script