[Misc] workflow: Use build environment#105
Merged
Merged
Conversation
Updated Sonar secret to be within this env
Pavan-SAP
enabled auto-merge (squash)
May 29, 2026 12:40
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
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.
Workflow: Scope Sonar Secret to Build Environment
Chore
🔧 Updated the CI workflow to associate the SonarCloud analysis job with the
buildenvironment, ensuring theSONAR_TOKENsecret is scoped to that environment. The redundantGITHUB_TOKENsecret reference has also been removed from the SonarCloud scan step.Changes
.github/workflows/ci.yml: Addedenvironment: buildto theanalysisjob so theSONAR_TOKENsecret is resolved from thebuildenvironment. Removed the now-unnecessaryGITHUB_TOKENenvironment variable from the SonarCloud scan step.PR Bot Information
Version:
1.21.0issue_comment.editedb986f8a2-4a17-4a77-839d-f7843f4981fa