Merge pull request #37009 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/test.yml

@@ -133,8 +133,6 @@ jobs:
         if: ${{ matrix.name == 'content-linter' }}
         uses: ./.github/actions/get-changed-files
         with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          pr: ${{ github.event.pull_request.number }}
           head: ${{ github.event.pull_request.head.ref || github.event.merge_group.head_ref }}
           output_file: get_diff_files.txt
 

content/admin/managing-your-enterprise-account/creating-an-enterprise-account.md

@@ -54,7 +54,7 @@ The following changes also apply to single organizations that are automatically
 * **Enterprise account name:** During the upgrade, the new enterprise account name will match your organization name or be as close as possible if taken. You can rename it after the upgrade.
 * **SAML SSO:** Existing SAML SSO will stay at the organization level after being added to the new enterprise account. You can configure SSO at the enterprise level post-upgrade, which will override the organization level. Existing PATs and SAML-authorized tokens will remain unchanged.
 * **Policies:** The new enterprise account starts with no policies, so existing organization policies won't be overridden.
-* **Spending limits:** Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, under "Settings" in the enterprise account sidebar, select **Billing**.
+* **Spending limits:** Existing organization spending limits transfer to the new enterprise account. Post-upgrade, billing is handled at the enterprise level. To adjust spending limits, at the top of the page, click {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**.
 * **Coupons:** Existing coupons will carry over to the new enterprise account with no interruptions.
 * **Workflow permissions:** The new enterprise account will inherit your organization's workflow permissions. If the organization has a permissive setting ("Read and write"), the enterprise account will also default to permissive. Otherwise, it defaults to restrictive ("Read repository contents and packages"). For workflows with the id-token permission, the default changes to read-only due to a February 2023 update. Add an explicit permissions block in these workflows to grant the required permissions.
 

content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md

@@ -24,7 +24,7 @@ To learn more about {% data variables.product.prodname_github_connect %}, see [A
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 
-1. On the left side of the page, in the enterprise account sidebar, click **GitHub Connect**.
+1. {% ifversion horizontal-nav %}At the top of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" %} **GitHub Connect**.{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "plug" aria-hidden="true" %} **GitHub Connect**.{% endif %}
 
 {% data reusables.server-statistics.csv-download %}
 

content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md

@@ -66,7 +66,7 @@ You can view the enterprise account's current license limits and usage.
 
 {% endif %}
 {%- ifversion ghec -%}
-1. Optionally, to see a detailed breakdown of usage per organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}, in the enterprise account sidebar, click **Billing**.
+1. Optionally, to see a detailed breakdown of usage per organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}, click {% octicon "credit-card" aria-hidden="true" %} **Billing & Licensing**.
 
    In the “{% data variables.product.prodname_GH_advanced_security %}” section, you can see a summary of your current license usage, as well as the number of committers and unique committers for each organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}. The organizations{% ifversion secret-scanning-user-owned-repos %} and user namespaces{% endif %} in the billing table are sorted by the highest number of unique committers in descending order.
 {% endif %}

content/billing/using-the-billing-platform/about-billing-for-your-enterprise.md

@@ -64,7 +64,7 @@ To check if you have access:
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 
-If you have access, there will be a **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing** option in the enterprise account sidebar.
+If you have access, there will be a **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing** option {% ifversion horizontal-nav %}at the top of the page.{% else %}in the enterprise account sidebar.{% endif %}
 
 {% endif %}
 

content/billing/using-the-new-billing-platform/roles-for-the-new-billing-platform.md

@@ -63,7 +63,7 @@ The invited person will receive an invitation email asking them to become a bill
 {% data reusables.profile.org_settings %}
 1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
 1. Click the link in the text box, **Enterprise account billing settings**, which will direct you to your organizations billing settings page.
-1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "person" aria-hidden="true" %} People**.
+1. {% ifversion horizontal-nav %}At the top of the page, click {% octicon "person" aria-hidden="true" %} **People**{% else %}On the left side of the page, in the enterprise account sidebar, click {% octicon "person" aria-hidden="true" %} **People**{% endif %}.
 1. Under "People", click **Administrators**.
 1. Above the list of administrators, click **Invite admin**.
 1. Type the username, full name, or email address of the person you want to invite, then select the appropriate person from the results.

content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md

@@ -29,6 +29,7 @@ You can use content exclusions to configure {% data variables.product.prodname_c
 * Code completion will not be available in the affected files.
 * The content in affected files will not inform code completion suggestions in other files.
 * The content in affected files will not inform {% data variables.product.prodname_copilot_chat %}'s responses.
+* Affected files will not be reviewed in a {% data variables.product.prodname_copilot_short %} code review.
 
 ### Who can configure content exclusion
 
@@ -44,8 +45,8 @@ Repository administrators{% ifversion ghec %}, organization owners, and enterpri
 | {% data variables.product.prodname_vscode %}    | {% octicon "check" aria-label="Supported" %}  |           {% octicon "check" aria-label="Supported" %}           |
 | JetBrains IDEs                                  | {% octicon "check" aria-label="Supported" %}  |           {% octicon "check" aria-label="Supported" %}           |
 | Vim/Neovim                                      | {% octicon "check" aria-label="Supported" %}  |                          Not applicable                          |
-| Xcode                                           | {% octicon "check" aria-label="Supported" %}  |                          Not applicable                          |
-| Eclipse                                         | {% octicon "check" aria-label="Supported" %}  | {% octicon "x" aria-label="Not supported" %} |
+| Xcode                                           | {% octicon "check" aria-label="Supported" %}  |           {% octicon "x" aria-label="Not supported" %}           |
+| Eclipse                                         | {% octicon "check" aria-label="Supported" %}  |           {% octicon "x" aria-label="Not supported" %}           |
 | Azure Data Studio                               | {% octicon "x" aria-label="Not supported" %}  |                          Not applicable                          |
 | The {% data variables.product.github %} website |                Not applicable                 |           {% octicon "check" aria-label="Supported" %}           |
 | {% data variables.product.prodname_mobile %}    |                Not applicable                 |           {% octicon "check" aria-label="Supported" %}           |

data/features/horizontal-nav.yml

@@ -0,0 +1,5 @@
+# Reference: #17228
+# Move Enterprise navigation from left sidebar to top of page
+versions:
+  ghec: '*'
+  ghes: '>3.16'

data/reusables/billing/enterprise-billing-menu.md

@@ -1 +1 @@
-1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing & Licensing**.{% endif %}

data/reusables/code-scanning/click-code-security-enterprise.md

@@ -1 +1 @@
-1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "shield" aria-hidden="true" %} Code Security**.
+1. {% ifversion horizontal-nav %}At the top of the page, click **{% octicon "shield" aria-hidden="true" %} Code Security**.{% else %}On the left side of the page, in the enterprise account sidebar, click **{% octicon "shield" aria-hidden="true" %} Code Security**.{% endif %}