From 90584bc98b5f2921da87be1af13c331a29df4862 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krist=C3=B3f=20Umann?= Date: Mon, 9 Oct 2023 10:14:36 +0200 Subject: [PATCH] Move docs changes from #4013 to this PR --- docs/web/diff.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/web/diff.md b/docs/web/diff.md index e082a547cd..39fce267e3 100644 --- a/docs/web/diff.md +++ b/docs/web/diff.md @@ -760,7 +760,7 @@ You can also name timestamps which we call tags. In the below image, the cogwhee Comparing runs and comparing tags/timestamps has a subtle difference: * For runs, we check whether a report is outstanding _at the time of the query_. This means, as seen [in a previous example](diff.md#example-setup-1), if you store a report, _and then_ set a false positive review status rule for it, _and then_ diff this _run_ against another, the report **will not be** present in the run's outstanding reports set. -* For tags/timestamps, we check whether a report is outstanding _before that specific tag/timestamp_. This means that if you store a report under `tag1`, _and then_ set a false positive review status rule for it, _and then_ diff this _tag_ against another, the report **will be** present in the tag's outstanding report set. +* For tags/timestamps, we check whether a report is outstanding _before that specific tag/timestamp_. This means that if you store a report under `tag1`, _and then_ set a false positive review status rule for it, _and then_ diff this _tag_ against another, the report **will be** present in the tag's outstanding report set. This also implies that **we ignore the detection status of the report**. :warning: Note: Tags are created when the report is stored. As a result, you can diff a local analysis directory against a remote tag, but there are no "local tags".