From bf92597c920fed192e1ff1542db58ee90d01d1c9 Mon Sep 17 00:00:00 2001
From: Philip Wedemann <22521688+hfhbd@users.noreply.github.com>
Date: Wed, 10 Aug 2022 00:16:40 +0200
Subject: [PATCH] Docs: GitHub - Add link to configure Sarif severity alert
 level (#5206)

* Docs: GitHub - Add link to configure Sarif severity alert level

* Remove unnecessary trailing space

Co-authored-by: schalkms <30376729+schalkms@users.noreply.github.com>
---
 website/docs/introduction/reporting.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/docs/introduction/reporting.md b/website/docs/introduction/reporting.md
index eb7be2611ff..922d638561e 100644
--- a/website/docs/introduction/reporting.md
+++ b/website/docs/introduction/reporting.md
@@ -138,6 +138,8 @@ subprojects {
 If your repository is hosted on Github, you can enable SARIF output in your repository.
 You can follow to the [official documentation](https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github).
 
+To change the severity level to fail your GitHub Action build configure it in [GitHub Settings](https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure).
+
 You can follow the example below as a quick start:
 ```yaml
 jobs: