We are currently using the Community Edition of SonarQube. We primarily use Go in our repositories and require additional custom rules beyond the default ones provided by SonarQube.
Is it possible for us to create these custom rules? If so, could you provide guidance on how to do that?
Hey there.
I suggest looking at the documentation on Adding Coding Rules, which indicates that you can only add custom rules to SonarQube using generic issue reports or external analyzer reports.
For what it’s worth, SAST for Go is on our roadmap.
You can also suggest new rules to be implemented here: New rules / language support - Sonar Community
Before implementing a new coding rule, you should consider whether it is specific to your own context or might benefit others. If it might benefit others, you can propose it on the community forum. If there is a shared interest, then it might be implemented for you directly in the related language plugin. It means less maintenance for you and benefit to others.