Merge branch 'main' into actions-sha

data/features/debug-reruns.yml

@@ -0,0 +1,7 @@
+# Issue 6629
+# Enabling debug logging when re-running jobs or workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6629'

data/features/secret-scanning-alert-audit-log.yml

@@ -0,0 +1,6 @@
+# Reference: #7046.
+# Documentation for new audit log events for alerts for secret scanning.
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-7046'

data/reusables/actions/about-artifact-log-retention.md

@@ -1,9 +1,12 @@
-By default, the artifacts and log files generated by workflows are retained for 90 days before they are automatically deleted. You can adjust the retention period, depending on the type of repository:
+By default, the artifacts and log files generated by workflows are retained for 90 days before they are automatically deleted.
+
+{%- ifversion fpt or ghec %}
+You can adjust the retention period, depending on the type of repository:
 
-{%- ifversion fpt or ghec or ghes %}
 - For public repositories: you can change this retention period to anywhere between 1 day or 90 days.
+- For private{% ifversion ghec %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days.
+{%- else %}
+You can change this retention period to anywhere between 1 day or 400 days.
 {%- endif %}
 
-- For private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days.
-
 When you customize the retention period, it only applies to new artifacts and log files, and does not retroactively apply to existing objects. For managed repositories and organizations, the maximum retention period cannot exceed the limit set by the managing organization or enterprise.

data/reusables/actions/enable-debug-logging-cli.md

@@ -0,0 +1 @@
+To enable enable runner diagnostic logging and step debug logging for the re-run, use the `--debug` flag.

data/reusables/actions/enable-debug-logging.md

@@ -0,0 +1,4 @@
+{% if debug-reruns %}
+1. Optionally, to enable runner diagnostic logging and step debug logging for the re-run, select **Enable debug logging**.
+   ![Enable debug logging](/assets/images/help/repository/enable-debug-logging.png)
+{% endif %}

data/reusables/audit_log/git-events-export-limited.md

@@ -0,0 +1,7 @@
+{% ifversion ghec %}
+{% note %}
+
+**Note:** When you export Git events, events that were initiated via the web browser or the REST or GraphQL APIs are not included. For example, when a user merges a pull request in the web browser, changes are pushed to the base branch, but the Git event for that push is not included in the export. 
+
+{% endnote %} 
+{% endif %}

data/reusables/education/upgrade-organization.md

@@ -1,2 +0,0 @@
-1. Next to the organization you want to upgrade, click **Upgrade**.
-  ![Upgrade button](/assets/images/help/education/upgrade-org-button.png)

data/reusables/education/upgrade-page.md

@@ -1 +0,0 @@
-1. Go to "Upgrade your organization" on the [Organization Upgrades](https://education.github.com/toolbox/offers/github-org-upgrades) page.

data/reusables/pages/about-private-publishing.md

@@ -1,5 +1,5 @@
 {% ifversion fpt %}
 You can create {% data variables.product.prodname_pages %} sites that are publicly available on the internet. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also publish sites privately by managing access control for the site.
 {% elsif ghec %}
-Unless your enterprise uses {% data variables.product.prodname_emus %}, you can choose to publish sites publicly or privately by managing access control for the site. 
+Unless your enterprise uses {% data variables.product.prodname_emus %}, you can choose to publish project sites publicly or privately by managing access control for the site. 
 {% endif %}