From 372a8874f076bf64ab9cb30fc5a4a84d4872c90f Mon Sep 17 00:00:00 2001 From: Konrad Pabjan Date: Tue, 11 Jul 2023 07:42:40 -0400 Subject: [PATCH] [Checks] Update documentation for checks retention (#38837) Co-authored-by: Matt Pollard --- data/reusables/pull_requests/retention-checks-data.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/reusables/pull_requests/retention-checks-data.md b/data/reusables/pull_requests/retention-checks-data.md index 5b2127d791..b4f16ef067 100644 --- a/data/reusables/pull_requests/retention-checks-data.md +++ b/data/reusables/pull_requests/retention-checks-data.md @@ -1,6 +1,6 @@ {% ifversion fpt or ghec %} -{% data variables.location.product_location %} retains check data for 400 days. After 400 days, the data is archived. +{% data variables.location.product_location %} retains checks data for 400 days. After 400 days, the data is archived. 10 days after archival, the data is permanently deleted. {% elsif ghes %} @@ -8,4 +8,4 @@ Site administrators can control the retention policy for checks data on {% data {% endif %} -For archived check data, a rollup commit status appears that represents the state of all of the checks for the commit. To merge a pull request with checks that are both required and archived, you must rerun the checks. +{% ifversion ghes < 3.10 %} For archived checks data, a rollup commit status appears that represents the state of all of the checks for the commit. {% endif %} To merge a pull request with checks that are both required and archived, you must rerun the checks.