Sonar-scanner branch analysis across forks, without creating a pull request

Hi Team,
I am trying to run sonar analysis on my local changes which would eventually be merged to github REMOTE/master.
Pull request analysis would be an easy way to do so, which is in place, but my entire PR verify job takes a lot of time as there are other tests/jobs that runs on the PR apart from sonar. As a result the feedback time to developer is a lot.

I have tried running branch analysis, which analyses within my-fork. my-branch to my-master

Is it possible to run sonar-scanner branch analysis across forks with :
sonar.branch.name =< my local branch , it could be my local master too>
sonar.branch.target = <REMOTE/master>

Please suggest a solution to this.

** Sonar versions used:
SonarQube server 7.9.1
SonarQube Scanner 4.1.0.1829

Hi Ajay, welcome to the SonarSource Community!

Now that the SonarQube 8.9 release has replaced 7.9 as the LTS, we no longer have an actively supported version of SonarQube that has the notion of “targets” for branches outside the context of a Pull Request. Short-lived branches were removed as a concept in 8.x

Our answer for developers looking for the earliest possible static analysis feedback is SonarLint.