Remove all ifversion that has all versions (6) (#49491)

content/repositories/archiving-a-github-repository/backing-up-a-repository.md

@@ -53,13 +53,13 @@ You can restore your backup by decompressing the archive and then pushing the wi
 
 You can use the REST API to generate a migration archive for a repository. For more information, see "[AUTOTITLE](/rest/migrations/orgs)."
 
-These archives are designed for moving data between {% data variables.product.prodname_dotcom %} products, but they can also be used {% ifversion fpt or ghec %}to back up a repository for archiving purposes{% else %} as backups.{% endif %}{% ifversion fpt or ghec or ghes %}
+These archives are designed for moving data between {% data variables.product.prodname_dotcom %} products, but they can also be used {% ifversion fpt or ghec %}to back up a repository for archiving purposes{% else %} as backups.{% endif %}
 
 {% warning %}
 
 **Warning:** Migration archives do not include all data related to a repository. For example, {% data variables.large_files.product_name_long %} objects, discussions, or packages are not included. For more information on what is included in migration archives, see "[AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products)."
 
-{% endwarning %}{% endif %}
+{% endwarning %}
 
 Once you have generated an archive, you can move it to a location of your choice for safe-keeping.
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md

@@ -1,7 +1,7 @@
 ---
 title: Renaming a branch
 intro: You can change the name of a branch in a repository.
-permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec or ghes %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec or ghes %} and protected branches{% endif %}.'
+permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch) or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches). People with admin permissions can rename the default branch and protected branches.'
 versions:
   fpt: '*'
   ghes: '*'

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md

@@ -168,12 +168,9 @@ Before you can require a linear commit history, your repository must allow squas
 
 {% endif %}
 
-{% ifversion fpt or ghec or ghes %}
-
 ### Require deployments to succeed before merging
 
 You can require that changes are successfully deployed to specific environments before a branch can be merged. For example, you can use this rule to ensure that changes are successfully deployed to a staging environment before the changes merge to your default branch.
-{% endif %}
 
 {% ifversion lock-branch %}
 

content/repositories/releasing-projects-on-github/about-releases.md

@@ -28,9 +28,7 @@ Anyone with read access to a repository can view and compare releases, but only
 
 You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[AUTOTITLE](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
 
-{% ifversion fpt or ghec or ghes %}
 When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
-{% endif %}
 
 GitHub will automatically include links to download a zip file and a tarball containing the contents of the repository at the point of the tag's creation.
 

content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md

@@ -40,7 +40,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 {% data reusables.releases.release-title %}
 1. In the "Describe this release" field, type a description for your release.
    If you @mention anyone in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
-   {% ifversion fpt or ghec or ghes %} Alternatively, you can automatically generate your release notes by clicking {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% endif %}
+    Alternatively, you can automatically generate your release notes by clicking {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.
 {% data reusables.releases.finish-release %}
 
 {% endwebui %}

content/rest/actions/permissions.md

@@ -16,6 +16,6 @@ autogenerated: rest
 
 ## About permissions for {% data variables.product.prodname_actions %}
 
-You can use the REST API to set permissions for the {% ifversion ghes or ghec %}enterprises, {% endif %}organizations and repositories that are allowed to run {% data variables.product.prodname_actions %}, and the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that are allowed to run.{% ifversion fpt or ghec or ghes %} For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."{% endif %}
+You can use the REST API to set permissions for the {% ifversion ghes or ghec %}enterprises, {% endif %}organizations and repositories that are allowed to run {% data variables.product.prodname_actions %}, and the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that are allowed to run. For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)."
 
 <!-- Content after this section is automatically generated -->

content/rest/rate-limit/rate-limit.md

@@ -30,7 +30,7 @@ The REST API for searching items has a custom rate limit that is separate from t
 
 - The `integration_manifest` object provides your rate limit status for the `POST /app-manifests/{code}/conversions` operation. For more information, see "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/creating-a-github-app-from-a-manifest#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration)."
 
-{% ifversion fpt or ghec or ghes %}* The `dependency_snapshots` object provides your rate limit status for submitting snapshots to the dependency graph. For more information, see "[AUTOTITLE](/rest/dependency-graph)."{% endif %}
+fpt or ghec or ghes %}* The `dependency_snapshots` object provides your rate limit status for submitting snapshots to the dependency graph. For more information, see "[AUTOTITLE](/rest/dependency-graph)."
 
 - The `code_scanning_upload` object provides your rate limit status for uploading SARIF results to code scanning. For more information, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)."
 

content/support/learning-about-github-support/about-github-support.md

@@ -73,9 +73,7 @@ You can contact {% data variables.contact.github_support %} in English.
 With {% data variables.product.product_name %}, you have access to support in English and Japanese.
 {% endif %}
 
-{% ifversion fpt or ghec or ghes %}
 {% data reusables.support.support-ticket-translation-option %}
-{% endif %}
 
 {% ifversion ghes or ghec %}
 

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

@@ -1 +1 @@
-By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized.{% ifversion fpt or ghec or ghes %} For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}
+By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and this retention period can be customized. For more information, see "[AUTOTITLE](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."