Ok, I would like to amend my previous statement, indeed you can still achieve a PR decoration without going to SQ project configuration and configure everything. Sorry for the confusion.
So on Azure, you have two possibilities:
- Use the currently documented process, have your SQ project
Pull Request settings configured (and in that case, you need to specify all parameters, including the name/repo)
- Have all the parameters in the scanner context, and you will get the warning you mentioned in your first thread.
Yes, despite the deprecation. This behaviour has been deprecated in 8.6, so it cannot be removed before SonarQube 10.x series (see our deprecation strategy here)
For Gitlab specifically, no it’s not under our radar for LTS 8.x.
What we have though is an objective for 2021 to reduce the friction (time and effort) it takes to setup and analyzes a project. What we have in mind is ease the automation of projects setup, one possible solution being introducing SQ configuration as code in the repo. Not sure that would be the implemented solution, but we are committed to improve the flow for enterprise with a lot of projects to configure.
PS: we listed this community discussion as insight to nurture the internal discussion on this topic