sonar-css-plugin is no longer used and the sonar-css repository is archived. Rules that are only in
sonar-css should be considered as deleted and rules that are moved in sonarJS should be displayed
as in sonarJS.
The current coverage format cannot represent perfectly this repository change, so removing sonar-css
from the list seems like the simplest approach to get a good enough result.
Replaced the old reference to slang-enterprise with references to split
repos and JIRA projects for each of the former SLang languages (Apex, Go, Ruby and Scala).
* Fix SQ issue Unexpected string concatenation
* Allow testing of the coverage update workflow by checking out all
branches and referencing the SHA of the triggering event
* Fix repository url for coverage update
* Add a manual trigger for coverage update
When there are multiple sonarpedia.json files for the same language, the rules
picked up for the next sonarpedia.json file will override the ones picked up
previously. With this fix, the rules are not overwritten but all are collected,
so one repository can have multiple sonarpedia.json files for the same language.
This removes the dependency on online repositories (on GitHub)
and speeds up the test by stripping the number of versions and files to a minimum.
Prepare the ground for RULEAPI-753.