Merge pull request #37432 from github/repo-sync

Repo sync

Author: docs-bot

content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md

@@ -38,7 +38,7 @@ Commits will appear on your contributions graph if they meet **all** of the foll
   * In the repository's default branch
   * In the `gh-pages` branch (for repositories with project sites)
 
-For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+For more information on project sites, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites).
 
 In addition, **at least one** of the following must be true:
 * You are a collaborator on the repository or are a member of the organization that owns the repository.
@@ -83,7 +83,7 @@ Generic email addresses, such as `[email protected]`, cannot be added to {% da
 
 ### Commit was not made in the default or `gh-pages` branch
 
-Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites).
 
 If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following:
 * [Open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch.

content/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md

@@ -54,7 +54,7 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun
 
 ## {% data variables.product.prodname_pages %}
 
-* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. See [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users).
+* {% data variables.enterprise.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. See [AUTOTITLE](/pages/getting-started-with-github-pages/github-pages-limits#limits-for-enterprise-managed-users).
 
 ## Interactions
 

content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md

@@ -138,11 +138,17 @@ After using `git-filter-repo` to remove the sensitive data and pushing your chan
 1. Contact {% data variables.contact.contact_support %}, and provide the following information:
 
     * The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
+{%- ifversion fpt or ghec %}
     * The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
+{%- endif %}
+{%- ifversion ghes %}
+    * The number of affected pull requests, found in the previous step. This is used by your site administrator to verify you understand how much will be affected.
+{%- endif %}
     * The First Changed Commit(s) reported by `git-filter-repo` (Look for `NOTE: First Changed Commit(s)` in its output.)
     * If `NOTE: There were LFS Objects Orphaned by this rewrite` appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.
 
-    If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:
+    {% ifversion fpt or ghec %}If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:{% endif %}
+    {% ifversion ghes %}If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, your site administrator will then:{% endif %}
 
     * Dereference or delete any affected PRs on {% data variables.product.github %}.
     * Run a garbage collection on the server to expunge the sensitive data from storage.

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md

@@ -35,12 +35,6 @@ body:
 
 You can set the following top-level keys for each issue form.
 
-{% ifversion issue-types %}
-
-{% data reusables.issues.release-stage %}
-
-{% endif %}
-
 | Key | Description | Required | Type |
 | :-- | :-- | :-- | :-- |
 | `name` | A name for the issue form template. Must be unique from all other templates, including Markdown templates. | Required | String |

content/copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md

@@ -14,9 +14,14 @@ redirect_from:
   - /copilot/github-copilot-enterprise/overview/enabling-github-copilot-enterprise-features
 ---
 
-## 1. Subscribe your enterprise to {% data variables.product.prodname_copilot %}
+## 1. Enable {% data variables.product.prodname_copilot %} in your Enterprise through payment verification
 
-Set up a subscription to {% data variables.product.prodname_copilot_enterprise_short %} or {% data variables.product.prodname_copilot_business_short %} for your enterprise. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/subscribing-to-copilot-for-your-enterprise).
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. Click the **{% octicon "check-circle" aria-hidden="true" %} Getting Started** tab.
+1. Under "Next steps", click **Verify your payment method**. This will enable {% data variables.product.prodname_copilot %} in your enterprise.
+
+After you've completed these steps, you will be able to confirm that {% data variables.product.prodname_copilot %} is enabled in your enterprise's **{% octicon "law" aria-hidden="true" %} Policies** tab.
 
 ## 2. Set policies
 

content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md

@@ -233,8 +233,6 @@ You can also use a <code>&ast;</code> as a wildcard.
 
 If your organization uses issue types, you can filter for particular types.
 
-{% data reusables.issues.release-stage %}
-
 | Qualifier  | Example
 | ---------- | -------------
 | <code>type:&quot;<em>ISSUE TYPE</em>&quot;    | **type:&quot;bug&quot;** will show issues with the "bug" type.
@@ -247,8 +245,6 @@ If your organization uses issue types, you can filter for particular types.
 
 You can filter your sub-issues by their parent issue.
 
-{% data reusables.issues.release-stage %}
-
 | Qualifier  | Example
 | ---------- | -------------
 | <code>parent-issue:<em>OWNER/REPO#ISSUE NUMBER</em></code> | **parent-issue:octocat/game#4** will show issues with issue #4 in octocat/game as their parent issue.

content/issues/tracking-your-work-with-issues/configuring-issues/managing-issue-types-in-an-organization.md

@@ -10,8 +10,6 @@ shortTitle: 'Managing issue types'
 permissions: 'Organization owners can modify issue types.'
 ---
 
-{% data reusables.issues.release-stage %}
-
 You can use issue types to classify and manage different types of issues across your organization. You can create up to {% data variables.projects.issue_type_limit %} issue types that your organization members can apply to issues, making it easier for you and your members to find issues and plan work.
 
 Default issue types are included in every organization, but these can edited, disabled, or deleted. The default types are task, bug, and feature.

content/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project.md

@@ -88,8 +88,6 @@ Below we have added a task list to our Project Octocat issue, breaking it down i
 
 ### Breaking down your work with sub-issues
 
-{% data reusables.issues.release-stage %}
-
 {% data reusables.issues.about-sub-issues %} See [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues) and [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/browsing-sub-issues).
 
 {% endif %}

content/issues/tracking-your-work-with-issues/using-issues/editing-an-issue.md

@@ -42,8 +42,6 @@ You can also make changes to the issue description. The edit history is availabl
 
 ## Adding or changing the issue type
 
-{% data reusables.issues.release-stage %}
-
 You can add an issue type or make changes to an existing issue type.
 
 1. Navigate to the issue you want to edit.

content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md

@@ -34,7 +34,7 @@ We recommend always using a `www` subdomain, even if you also use an apex domain
 
 ## Using a custom domain across multiple repositories
 
-If you set a custom domain for a user or organization site, by default, the same custom domain will be used for all project sites owned by the same account. For more information about site types, see [AUTOTITLE](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+If you set a custom domain for a user or organization site, by default, the same custom domain will be used for all project sites owned by the same account. For more information about site types, see [AUTOTITLE](/pages/getting-started-with-github-pages/what-is-github-pages#types-of-github-pages-sites).
 
 For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`.