Merge pull request github#24285 from github/repo-sync

repo sync

Author: Octomerger

content/admin/configuration/configuring-your-enterprise/configuring-applications.md

@@ -21,3 +21,16 @@ You can choose the amount of time that {% data variables.location.product_locati
 3. In the "Settings" sidebar, click **Applications**.
 4. Under "Avatar image cache time (seconds)", type the number of seconds that you would like {% data variables.location.product_location %} to cache avatar images.
 {% data reusables.enterprise_management_console.save-settings %}
+
+{% ifversion status-check-retention %}
+## Enabling retention policy for checks
+You can enable a retention policy for checks, actions, and associated data by setting thresholds for archival and deletion. For more information about configuring actions, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. In the "Settings" sidebar, click **Checks**.
+2. Select **Enable archiving of Checks-related data**.
+3. Under "Archive threshold (days)", type the number of days for the archival threshhold. Checks older than this number of days will be archived. 
+4. Under "Delete threshold (days)", type the number of days for the deletion threshhold. Archived checks older than this number of days will be permanently deleted. 
+{% data reusables.enterprise_management_console.save-settings %}
+{% endif %}

content/code-security/secret-scanning/secret-scanning-patterns.md

@@ -41,7 +41,15 @@ If you believe that {% data variables.product.prodname_secret_scanning %} should
 
 {% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
 
-{% data reusables.secret-scanning.partner-secret-list-public-repo %}
+<!-- PUBLIC TABLE STARTS HERE -->
+<!-- This recreates the table in the now deleted data/reusables/secret-scanning/partner-secret-list-public-repo.md -->
+Partner | Supported secret
+--- | ---
+{%- for entry in secretScanning.isPublic %}
+{{ entry.provider }} | {{ entry.supportedSecret }}
+{%- endfor %}
+<!-- PUBLIC TABLE ENDS HERE -->
+
 {% endif %}
 
 ## Supported secrets for {% ifversion fpt or ghec %}user {% endif %}alerts
@@ -60,7 +68,14 @@ If you use the REST API for secret scanning, you can use the `Secret type` to re
 {% endnote %}
 {% endif %}
 
-{% data reusables.secret-scanning.partner-secret-list-private-repo %}
+<!-- PRIVATE TABLE STARTS HERE -->
+<!-- This recreates the table in the now deleted data/reusables/secret-scanning/partner-secret-list-private-repo.md. -->
+Provider | Supported secret | Secret type
+--- | --- | ---
+{%- for entry in secretScanning.isPrivateWithGhas %}
+{{ entry.provider }} | {{ entry.supportedSecret }} | {{ entry.secretType }} |
+{%- endfor %}
+<!-- PRIVATE TABLE ENDS HERE -->
 
 {% ifversion secret-scanning-push-protection %}
 ## Supported secrets for push protection
@@ -71,7 +86,14 @@ If you use the REST API for secret scanning, you can use the `Secret type` to re
 
 {% data reusables.secret-scanning.push-protection-older-tokens %} For more information about push protection limitations, see "[AUTOTITLE](/code-security/secret-scanning/troubleshooting-secret-scanning#push-protection-and-pattern-versions)."
 
-{% data reusables.secret-scanning.secret-list-private-push-protection %}
+<!-- PUSH PROTECTION TABLE STARTS HERE -->
+<!-- This recreates the table in the now deleted data/reusables/secret-scanning/secret-list-private-push-protection.md -->
+Provider | Supported secret | Secret type
+--- | --- | ---
+{%- for entry in secretScanning.hasPushProtection %}
+{{ entry.provider }} | {{ entry.supportedSecret }} | {{ entry.secretType }}
+{%- endfor %}
+<!-- PRIVATE TABLE ENDS HERE -->
 
 {% endif %}
 ## Further reading

content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md

@@ -79,8 +79,9 @@ Alternatively, to skip or request _all_ checks for your commit, add one of the f
   request-checks: true"
   ```
 
-{% ifversion fpt or ghec %}
+{% ifversion status-check-retention %}
 ### Retention of status checks
 
 {% data reusables.pull_requests.retention-checks-data %}
+
 {% endif %}

content/rest/guides/using-the-rest-api-to-interact-with-checks.md

@@ -93,7 +93,7 @@ When a user clicks the button, {% data variables.product.prodname_dotcom %} send
 
 For a detailed example of how to set up requested actions with the REST API, see "[AUTOTITLE](/apps/creating-github-apps/guides/creating-ci-tests-with-the-checks-api#part-2-creating-the-octo-rubocop-ci-test)."
 
-{% ifversion fpt or ghec %}
+{% ifversion status-check-retention %}
 ## Retention of checks data
 
 {% data reusables.pull_requests.retention-checks-data %}

data/features/status-check-retention.yml

@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.8'

data/release-notes/enterprise-server/3-8/0-rc1.yml

@@ -27,6 +27,8 @@ sections:
         # https://github.com/github/releases/issues/2759
         - |
           To establish or comply with internal policies, site administrators can use the Management Console to configure an instance's policy for retention of data related to checks, including checks data generated by GitHub Actions and the Statuses API. Administrators can enable or disable retention, set a custom retention threshold, or set a custom hard-delete threshold.
+          For more information, see "[Configuring applications](/admin/configuration/configuring-your-enterprise/configuring-applications)" [Updated: 2023-03-02]
+      
 
         # https://github.com/github/releases/issues/2814
         - |

data/reusables/pull_requests/retention-checks-data.md

@@ -1 +1,11 @@
-Checks data older than 400 days is archived. As part of the archiving process {% data variables.product.prodname_dotcom %} creates a rollup commit status representing the state of all of the checks for that commit. As a consequence, the merge box in any pull request with archived checks that are required will be in a blocked state and you will need to rerun the checks before you can merge the pull request.
+{% ifversion fpt or ghec %}
+
+{% data variables.location.product_location %} retains check data for 400 days. After 400 days, the data is archived.
+
+{% elsif ghes %}
+
+Site administrators can control the retention policy for checks data on {% data variables.location.product_location %}. For more information, see "[Configuring applications](/admin/configuration/configuring-your-enterprise/configuring-applications#enabling-retention-policy-for-checks)."
+
+{% 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.