Enterprise bug fix hour for the week of October 16, 2023 (#44770)

witaliy12 · Oct 23, 2023 · cb0f1c9 · cb0f1c9
1 parent b449c94
commit cb0f1c9
Show file tree

Hide file tree

Showing 5 changed files with 10 additions and 6 deletions.
diff --git a/...g-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/...g-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -38,7 +38,7 @@ After you enable {% data variables.product.prodname_github_connect %}, license d
 ### Triggering a license sync job
 
 1. Sign in to your {% data variables.product.prodname_ghe_server %} instance.
-{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.access-enterprise-ghes %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
 1. Under "License sync", click {% octicon "sync" aria-hidden="true" %} **Sync now**.
@@ -49,7 +49,8 @@ After you enable {% data variables.product.prodname_github_connect %}, license d
 
 You can download a JSON file from {% data variables.product.prodname_ghe_server %} and upload the file to {% data variables.product.prodname_ghe_cloud %} to manually sync user license usage between the two deployments.
 
-{% data reusables.enterprise-accounts.access-enterprise %}
+1. Sign in to your {% data variables.product.prodname_ghe_server %} instance.
+{% data reusables.enterprise-accounts.access-enterprise-ghes %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
 1. In the "User licenses" section, under "Quick links", to download a file containing your current license usage on {% data variables.product.prodname_ghe_server %}, click **Export license usage**.

diff --git a/content/code-security/secret-scanning/about-secret-scanning.md b/content/code-security/secret-scanning/about-secret-scanning.md
@@ -26,7 +26,7 @@ topics:
 
 If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project.
 
-{% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets{% ifversion ghec or ghes or ghae %}, even if the repository is archived{% endif %}. {% ifversion secret-scanning-issue-body-comments %}{% data reusables.secret-scanning.scan-issue-description-and-comments %}{% endif %}
+{% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets{% ifversion ghec or ghes or ghae %}, even if the repository is archived{% endif %}. {% ifversion secret-scanning-issue-body-comments %}{% data reusables.secret-scanning.scan-issue-description-and-comments %}{% else %}{% data variables.product.prodname_secret_scanning_caps %} does not scan issues.{% endif %}
 
 {% ifversion secret-scanning-backfills-historical-issues %}
 Additionally, {% data variables.product.prodname_secret_scanning %} scans the titles, descriptions, and comments, in open and closed historical issues, and reports leaked secrets as alerts on {% data variables.product.prodname_dotcom %}{% ifversion ghec %}. A notification is sent to the relevant partner when a historical partner pattern is detected{% endif %}.

diff --git a/content/rest/teams/external-groups.md b/content/rest/teams/external-groups.md
@@ -12,6 +12,8 @@ autogenerated: rest
 
 ## About external groups
 
+{% data reusables.scim.ghes-beta-note %}
+
 To use these endpoints, the authenticated user must be a team maintainer or an owner of the organization associated with the team.
 
 {% ifversion ghec %}

diff --git a/data/reusables/enterprise-accounts/access-enterprise-ghes.md b/data/reusables/enterprise-accounts/access-enterprise-ghes.md
@@ -0,0 +1,3 @@
+1. In the top-right corner of {% data variables.product.prodname_ghe_server %}, click your profile photo, then click **Enterprise settings**.
+
+    ![Screenshot of the drop-down menu that appears when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is highlighted in a dark orange outline.](/assets/images/enterprise/settings/enterprise-settings.png)
diff --git a/data/reusables/enterprise-accounts/access-enterprise.md b/data/reusables/enterprise-accounts/access-enterprise.md
@@ -4,7 +4,5 @@
 1. In the list of enterprises, click the enterprise you want to view.
 
 {%- elsif ghes or ghae %}
-1. In the top-right corner of {% data variables.product.product_name %}, click your profile photo, then click **Enterprise settings**.
-
-    ![Screenshot of the drop-down menu that appears when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is highlighted in a dark orange outline.](/assets/images/enterprise/settings/enterprise-settings.png)
+{% data reusables.enterprise-accounts.access-enterprise-ghes %}
 {%- endif %}
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,3 @@
		1. In the top-right corner of {% data variables.product.prodname_ghe_server %}, click your profile photo, then click Enterprise settings.

		![Screenshot of the drop-down menu that appears when you click the profile photo on GitHub Enterprise Server. The "Enterprise settings" option is highlighted in a dark orange outline.](/assets/images/enterprise/settings/enterprise-settings.png)