Hi Lucas,
Allow me to complement Ann’s answer with a broader view of SonarQube capabilities.
PDF reporting is only available at Portfolio level (see documentation). This is typically targeted for higher-level reporting, i.e. project stakeholders who would like to get a heads-up on key health indicators, and understand the codebase quality status at a glance.
SonarQube definitely intends to help developer clean their code, and it offers much more powerful features than PDF reports (which are quite static and missing context) to do that. Things like:
- SCM integration
- Code Viewer
- Notifications as Ann mentioned
- not to mention central Leak Period and Quality Gate concepts, and Branch/Pull-Request Analysis too
Those will all work together and allow your devs to be informed about any new issue in the code, with all information required to understand it in-situ, and get maximum knowledge to fix it appropriately.