Hi Ann,
I came across a post from two years ago that discussed the same issue I am currently facing. The post can be found at Sonar on Github Actions with Python Coverage "source" Issue.
When using the OSS version of sonarqube-scan-actions, the Sonar scan runs in a Docker container with the source volume mounted to a separate location. The following log is from the Docker command in the Github Action:
-v "/runner/work/repo":"/github/workspace"
As a result, Sonar Scanner is unable to recognize the /runner/work/repo path even though some of the report paths are using it. Ideally, we would like address this issue in OSS side. Please let me know if SonarQube team can resolve this problem. Thanks!