From 42dbcbe8f14abe3b11c1817a9126d3a7a0503aca Mon Sep 17 00:00:00 2001 From: Florian Verdonck Date: Tue, 17 Oct 2023 09:11:39 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: dawe --- docs/content/Running during CI.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/Running during CI.md b/docs/content/Running during CI.md index 5274f62..6504e9c 100644 --- a/docs/content/Running during CI.md +++ b/docs/content/Running during CI.md @@ -6,13 +6,13 @@ index: 5 # Running analyzers during continuous integration -Similar to unit tests and coding formatting, analyzers are a tool you want to enforce when modifying a code repository. +Similar to unit tests and code formatting, analyzers are a tool you want to enforce when modifying a code repository. Especially, in the context of a team, you want to ensure everybody is adhering to the warnings produced by analyzers. ## Command line options Use the `--report` command line argument to produce a [sarif](https://sarifweb.azurewebsites.net/) report json. -Most *CI/CD* system should be able to process this afterwards to capture the reported information by the analyzers. +Most *CI/CD* systems should be able to process this afterwards to capture the reported information by the analyzers. Example usage: