Is it mandatory to write CI/CD pipeline for each repo to know the current coverage on PR?

We have Sonarqube developer edition
And we have 100+ github repositories to onboard with quality gates(including coverage) enabled at PR level.
Is there any optimised way to integrate all these repos to sonarqube so that on each PR , we validate the quality checks and update the PR with quality gates status?
And to get coverage on new PR , should i write seperate pipeline for each git repo ?


Welcome to the community!

You didn’t mention which CI you use. As mentioned in the docs

SonarScanners running in Jenkins can automatically detect branches and Merge or Pull Requests in certain jobs. You don’t need to explicitly pass the branch or Pull Request details.

Meaning you shouldn’t need to set up specific branch/PR detection in each job.