From 70043750b4d5b98373555790ad52f2afe964f9e7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krist=C3=B3f=20Umann?= Date: Tue, 9 Jan 2024 09:59:00 +0100 Subject: [PATCH] Update diff.md --- docs/web/diff.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/web/diff.md b/docs/web/diff.md index c99f0f65cf..f982d17dc3 100644 --- a/docs/web/diff.md +++ b/docs/web/diff.md @@ -29,10 +29,10 @@ remote-remote, and local-remote or remote-local diffs. Generally speaking, diff allows you to express high level source code quality questions: * Serverless Pull Request Analysis: Both the analysis result of the baseline (e.g. master branch) and the new code (e.g. soon-to-be pull request) is stored in local report folders, which are then compared to find out new/resolved reports. -* Local/Server Pull Request Analysis: The analysis of a new code (e.g. soon-to-be pull request) is stored locally, while the baseline (e.g. master branch) is on the server, and the new (modified) version of code is analyzed to a local report folder. -* Server based Pull Request Analysis: Both the analysis result of the baseline (e.g. master branch) and the new code (e.g. pull request) is located on the server and the user wants to find out new/resolved reports in the PR. -* Server based branch history analysis: The user wants to find out analysis result differences of two analysis instances of the same branch to know which reports were fixed or introduced in e.g. the last month. - +* Local/Server Pull Request Analysis: The analysis of a new code (e.g. soon-to-be pull request) is stored locally, while the baseline (e.g. master branch) is on the server. +* Server based Pull Request Analysis: Both the analysis result of the baseline (e.g. master branch) and the new code (e.g. pull request) is located on the server. +* Server based branch history analysis: When making changes to a pull request / branch, analyses of the changes can be stored on the same run. This can be used whether a change on the PR/branch fixed or introduced a new bug. +* This allows you to add CodeChecker to your CI loops by checking if a patch introduced a new bug, and you can identify if a patch fixed an existing bug. :warning: Note: When calculating diff results, reports are uniqued. For more information see [analyzer report identification](../analyzer/report_identification.md).