You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following idea for an enhancement: it would be great if the name of the status check on a pull request would be configurable. At the moment it is hard-coded to <project-name> Sonarqube Results, see the source code.
Which leads to a status check like this (where sonarqube-test is the project name):
This makes it hard to apply global policies for required status checks in GitHub, because the name differs per project. As an example: there is a global policy we apply to all GitHub repositories that a status check called "Jenkins" is required to pass before a PR could be merged. That is no problem, because the status check is called "Jenkins" for every repository.
If I would like to do the same for SonarQube, I would need to adjust the name of the status check in every repository, e.g.:
If I could support by testing a new plugin version or similar, I would be happy to do so.
The text was updated successfully, but these errors were encountered:
@alexbde We faced the same problem, if you can't wait you can do what we did and forked the plugin and changed the status check name. If you don't want to do that you can use the github api to set the custom sonarqube status check for every repo.
we are also facing the same issue and this problem started happening after upgrading sonarqube from 7.X to 8.X, before that we had a universal name for all checks...after the upgrade the check name changed with project name as prefix
Hi, for information in the "Developer" edition (paid), GitHub status check has a fixed name SonarQube Code Analysis
Maybe could be relevant to align to this behavior...
Hi!
Following idea for an enhancement: it would be great if the name of the status check on a pull request would be configurable. At the moment it is hard-coded to
<project-name> Sonarqube Results
, see the source code.Which leads to a status check like this (where
sonarqube-test
is the project name):This makes it hard to apply global policies for required status checks in GitHub, because the name differs per project. As an example: there is a global policy we apply to all GitHub repositories that a status check called "Jenkins" is required to pass before a PR could be merged. That is no problem, because the status check is called "Jenkins" for every repository.
If I would like to do the same for SonarQube, I would need to adjust the name of the status check in every repository, e.g.:
If I could support by testing a new plugin version or similar, I would be happy to do so.
The text was updated successfully, but these errors were encountered: