ci: support sonar runs for forks#163
Merged
Merged
Conversation
|
gm42
approved these changes
Mar 3, 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
2 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.
Description
The Sonarcloud step of the "PR checks" workflow for forks is failing, because GHA for forks can't access repository secrets to prevent secret extraction.
This patch splits the PR pipeline. The coverage report is created on the fork and uploaded as a GH artefact. Once the fork "PR Checks" workflow passed, a workflow that runs in the scope of the base repository is triggered, which has access to the Sonarcloud repository secret to analyse the report.