Thanks for the guidance. When I’m on the PR’s Issues page, if I click on “All” for all issues, I see the number of Fixed is 2. If I click on “My Issues”, I see the following:
Notice that 3 of the lines are gray, including the “Fixed”, which also shows “0”. If you hover your mouse over that line, you see a “not available” sign in gray pop up. Interesting.
As far as viewing the branch, not the PR, I do not see a way to do that. All of my links are to the PR. Also, I checked the branch listing for this project in the SQ UI and I only see one branch listed there: “master”.
I wonder if this could be because this was an old SQ project, before the GitHub PR integration, that was converted to a GitHub Integration? Does that make sense? We’ve had it a while and in the last 6-12 months when we upgraded our SQ instance, we decided to move to using the GitHub integration (our GitHub is also on prem). Some projects were created new, but projects with a lot of data were just converted to use the GitHub Integration.
Regarding your question about the prereqs, I believe they are. We don’t explicitly set the branch name, but it should be derived from the environment. Here is that section of the GitHub workflow:
- name: Run SonarQube Checks
uses: sonarsource/sonarqube-scan-action@v5.0.0
env:
SONAR_HOST_URL: ${{ vars.SONAR_HOST_URL }}
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
SONAR_ROOT_CERT: ${{ secrets.CERT_CHAIN }}
SONAR_USER_HOME: ${{ env.SONAR_RUNNER_HOME }}/.sonar
with:
args: >
-Dsonar.projectKey=web
-Dsonar.sources=modules,report-templates,scripts
-Dsonar.exclusions=web/js/**web/css/**
-Dsonar.tests=tests,tests_functional
-Dsonar.scm.provider=git
-Dsonar.python.version=3.6
I will check to see if our projects that were created as a GitHub Integration have any differences.
Update: I checked and I see “not available” for some projects that I know were created as GitHub Integration projects.
