Bug fixes for Enterprise content, 2022-09-29 (github#31278)

Author: mattpollard

content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md

@@ -21,7 +21,8 @@ You can authorize an existing personal access token, or [create a new personal a
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
 {% data reusables.user-settings.personal_access_tokens %}
-3. Next to the token you'd like to authorize, click **Configure SSO**.
+3. Next to the token you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %}
+
    ![Screenshot of the dropdown menu to configure SSO for a personal access token](/assets/images/help/settings/sso-allowlist-button.png)
 4. To the right of the organization you'd like to authorize the token for, click **Authorize**.
    ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)

content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md

@@ -26,7 +26,7 @@ You can authorize an existing SSH key, or create a new SSH key and then authoriz
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.ssh %}
-1. To the right of the SSH key you'd like to authorize, click **Configure SSO**.
+1. To the right of the SSH key you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %}
 
    ![Screenshot of the SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
 1. To the right of the organization you'd like to authorize the SSH key for, click **Authorize**.

content/code-security/security-overview/filtering-alerts-in-the-security-overview.md

@@ -25,9 +25,11 @@ shortTitle: Filtering alerts
 
 You can use filters in the security overview to narrow your focus based on a range of factors, like alert risk level, alert type and feature enablement. Different filters are available depending on the specific view and whether your analysis is at the organization, team or repository level.
 
+{% ifversion security-overview-displayed-alerts %}
 {% note %}
 {% data reusables.security-overview.information-varies-GHAS %}
 {% endnote %}
+{% endif %}
 
 ## Filter by repository
 

content/code-security/security-overview/viewing-the-security-overview.md

@@ -4,7 +4,7 @@ intro: Navigate to the different views available in the security overview
 permissions: '{% data reusables.security-overview.permissions %}'
 product: '{% data reusables.gated-features.security-overview %}'
 versions:
-  ghae: '>= 3.5'
+  ghae: '>= 3.4'
   ghes: '*'
   ghec: '*'
 type: how_to

content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md

@@ -36,11 +36,11 @@ Dependency review is included in {% data variables.product.product_name %} for p
 1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
    ![Screenshot of GitHub Advanced Security feature with "Enable" button emphasized](/assets/images/help/security/enable-ghas-private-repo.png)
 
-{% elsif ghes %}
-Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."
+{% elsif ghes or ghae %}
 
-### Checking if the dependency graph is enabled
+Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
 
+### Checking if the dependency graph is enabled
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -49,6 +49,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
 1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes < 3.3 %}
   ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %}
     ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %}
+
 {% endif %}
 
 {% ifversion dependency-review-action-configuration %}

data/features/commit-tree-view.yml

@@ -3,5 +3,5 @@
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>=3.6'
-  ghae: '>= 3.8'
+  ghes: '>=3.7'
+  ghae: '>=3.7'

data/reusables/enterprise_installation/hotpatching-explanation.md

@@ -1,3 +1,7 @@
-You can upgrade {% data variables.product.prodname_ghe_server %} to the latest patch release using a hotpatch, which does not require a maintenance window and usually does not require a reboot. 
+You can upgrade {% data variables.product.prodname_ghe_server %} to the latest patch release using a hotpatch.
 
 You can use hotpatching to upgrade to a newer patch release, but not a feature release. For example, you can upgrade from `2.10.1` to `2.10.5` because they are in the same feature series, but not from `2.10.9` to `2.11.0` because they are in a different feature series.
+
+Hotpatches do not generally require a reboot. If a hotpatch does require a reboot, the {% data variables.product.product_name %} release notes will indicate the requirement.
+
+Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.product.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."

data/reusables/saml/authenticate-with-saml-at-least-once.md

@@ -0,0 +1 @@
+If you don't see **Configure SSO**, ensure that you have authenticated at least once through your SAML IdP to access resources on {% data variables.product.product_location %}. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."