How to make sonarqube detect non-master branches?

@herminia_bruen 

To make SonarQube detect non-master branches, you can use Pull Request analysis feature, which supports analyzing branches separate from the main branch (usually master). Here are the steps to set it up:

1. Ensure your SonarQube server is correctly set up and connected to your code repository.
2. Install and configure the SonarQube Scanner on your CI/CD pipeline or development environment.
3. Make sure that your code repository is connected to SonarQube and that pull requests are enabled for analysis.
4. Configure your CI/CD pipeline to trigger SonarQube analysis for each pull request. You can either trigger it automatically for each pull request or manually before merging the pull request.
5. Set up your SonarQube project to analyze the pull requests separately from the main branch. This can usually be done in the project settings in the SonarQube dashboard.
6. Run the SonarQube analysis for each pull request by using the appropriate commands or configuration in your CI/CD pipeline.
7. View and analyze the SonarQube reports for each pull request to identify and fix code quality issues before merging the branch into the main branch.

By following these steps, you can ensure that SonarQube detects and analyzes non-master branches to maintain code quality and prevent the introduction of bugs and vulnerabilities into your codebase.