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
SonarQubeCloud has updated their plans, restricting the old free plan to only allow analysises on the main branch of a repository.
Users that registered with the former plan - now called Legacy Plan - can still analyze all branches.
However, according to their documentation, theses users (and organizations) will have to migrate to the new Free Plan soon.
Therefore it has been proposed to upgrade this repository to the Team Plan, once this change takes place.
We would then let SonarQubeCloud analyze on every PR.
This would provide addtional benefit in Forks not having to set up analyses themselves.
Actually, analyzation on PR is enabled by default.
We currently suppress it in CI:
...
upload_to_sonar:
runs-on: ubuntu-22.04name: Upload SonarQube analysis to sonarcloud# no pull request and not on releaseif: github.head_ref == '' && !startsWith(github.ref, 'refs/tags')...
To allow analysis for already affected (new) users, enabling analysis on PR shall be considered.
The text was updated successfully, but these errors were encountered:
SonarQubeCloud has updated their plans, restricting the old free plan to only allow analysises on the main branch of a repository.
Users that registered with the former plan - now called Legacy Plan - can still analyze all branches.
However, according to their documentation, theses users (and organizations) will have to migrate to the new Free Plan soon.
Therefore it has been proposed to upgrade this repository to the Team Plan, once this change takes place.
We would then let SonarQubeCloud analyze on every PR.
This would provide addtional benefit in Forks not having to set up analyses themselves.
Actually, analyzation on PR is enabled by default.
We currently suppress it in CI:
To allow analysis for already affected (new) users, enabling analysis on PR shall be considered.
The text was updated successfully, but these errors were encountered: