This issue prevents our team from running full analysis of protected branch (e.g. “develop”) automatically.
We use the CircleCI Developer Hub - sonarsource/sonarcloud orb from CircleCI
The output of the scan is expected to be:
" INFO: Branch name: develop, type: short-lived "
but the actual result is:
" INFO: Pull request 2001 for merge into master from develop "
To reproduce:
- Merge non-protected feature branch into protected (e.g. “develop”) branch
- Log into CircleCI
- Open step “SonarCloud“ of the job corresponding to the workflow triggered by the merge of feature branch into develop branch
- Find the line below the following one: INFO: Organization key: organizationkey
Any way we can do a full scan on the protected branches?