Manually triggered Github workflows on branches are pushed to main on sonarcloud.io

[pko]

Template for a good new topic, formatted with Markdown:

• ALM used: GitHub
• CI system used: GitHub
• Scanner command used: `./gradlew sonar --info
• Languages of the repository: Kotlin
• Error observed: When manually starting a workflow on a branch or tag, the results are publish on Sonarcloud.io as if run on the main branch. I expect this to be published as a branch run, shown in the Branches overview.
• Steps to reproduce: Manually trigger a Github workflow on a gradle project on a branch.
• Potential workaround: None known so far.

This seems to be the exact issue as described here: SonarCloud Github: always pushed to main branch on "workflow_dispatch"

[Colin]

Hey there!

We’ve seen this before. @sodul was kind enough to provide a workaround:

Sonarcloud-github-action publishes branch analysis to main and not the current branch

I was able to simplify the logic by doing just setting sonar.branch.name explicitly when not on a PR: sonar-project.properties: sonar.branch.name = ${env.SONAR_BRANCH} Then in a shell step of the workflow yaml: if [[ ! $GITHUB_BASE_REF ]]; then # GITHUB_BASE_REF is only set for PRs, we are on a branch. echo "SONAR_BRANCH=${GITHUB_REF_NAME}" >> $GITHUB_ENV fi This way the sonar.branch.name is the only parameter to set and only set if we are not on a pull r…

and I confirm there’s a ticket in our backlog to autoconfigure the branch when executed via workflow_dispatch