The pull request decoration for detect scan is formatted quite loudly (font is very large and bold). This gets especially messy when multiple PR builds run and each run comments. Compared to other scan tools like e.g. SonarQube, this is unnecessary:
Screenshots
![image](https://github.com/SAP/jenkins-library/assets/6208191/3e9d8164-3735-4a98-8561-3205a473f5b4)
vs
![image](https://github.com/SAP/jenkins-library/assets/6208191/a43740bc-efda-4e54-a4ca-e0dd43592f0c)
Also, the link pointing to the detect documentation 404s, and is not clickable since the header tags need to be outside of the <a> tags in GitHub Markdown.
This PR
fixes the URL to the detect documentation
replaces markup heading with bold font
replaces h3 tags with h4.
Screenshots
Before:
![image](https://github.com/SAP/jenkins-library/assets/6208191/e6600601-a700-409b-a6cf-a64d00d9166d)
after
![image](https://github.com/SAP/jenkins-library/assets/6208191/1be96100-3bfc-4f88-864f-ce04c5ff1775)
Changes
The pull request decoration for detect scan is formatted quite loudly (font is very large and bold). This gets especially messy when multiple PR builds run and each run comments. Compared to other scan tools like e.g. SonarQube, this is unnecessary:
Screenshots
![image](https://github.com/SAP/jenkins-library/assets/6208191/3e9d8164-3735-4a98-8561-3205a473f5b4) vs ![image](https://github.com/SAP/jenkins-library/assets/6208191/a43740bc-efda-4e54-a4ca-e0dd43592f0c)Also, the link pointing to the detect documentation 404s, and is not clickable since the header tags need to be outside of the
<a>
tags in GitHub Markdown.This PR
Screenshots
Before: ![image](https://github.com/SAP/jenkins-library/assets/6208191/e6600601-a700-409b-a6cf-a64d00d9166d) after ![image](https://github.com/SAP/jenkins-library/assets/6208191/1be96100-3bfc-4f88-864f-ce04c5ff1775)