repo sync

Author: Octomerger

content/actions/creating-actions/creating-a-javascript-action.md

@@ -267,4 +267,4 @@ From your repository, click the **Actions** tab, and select the latest workflow
 ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run-updated.png)
 {% else %}
 ![A screenshot of using your action in a workflow](/assets/images/help/repository/javascript-action-workflow-run.png)
-{% endif %}
+{% endif %}

content/actions/hosting-your-own-runners/about-self-hosted-runners.md

@@ -91,7 +91,7 @@ The following operating systems are supported for the self-hosted runner applica
 
 - macOS 10.13 (High Sierra) or later
 
-{% if currentVersion != "free-pro-team@latest" %}
+{% if enterpriseServerVersions contains currentVersion %}
 
 ### Supported actions on self-hosted runners
 

content/actions/hosting-your-own-runners/adding-self-hosted-runners.md

@@ -50,13 +50,13 @@ You can add self-hosted runners to an enterprise, where they can be assigned to
 
 {% if currentVersion == "free-pro-team@latest" %}
 To add a self-hosted runner to an enterprise account, you must be an enterprise owner.
-{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "[email protected]"%}
+{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]"%}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% endif %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.enterprise-accounts.access-enterprise %}
-{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "[email protected]"%}
+{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]"%}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.business %}
 {% endif %}

content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md

@@ -56,7 +56,7 @@ When creating a group, you must choose a policy that grants access to all organi
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.enterprise-accounts.access-enterprise %}
-{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "[email protected]"%}
+{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]"%}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.business %}
 {% endif %}

content/actions/hosting-your-own-runners/removing-self-hosted-runners.md

@@ -62,15 +62,15 @@ To remove a self-hosted runner from an organization, you must be an organization
 
 {% if currentVersion == "free-pro-team@latest" %}
 To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
-{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "[email protected]"%}
+{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]"%}
 To remove a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine.
 {% endif %}
 
 {% data reusables.github-actions.self-hosted-runner-reusing %}
 
 {% if currentVersion == "free-pro-team@latest" %}
 {% data reusables.enterprise-accounts.access-enterprise %}
-{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "[email protected]"%}
+{% else if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "[email protected]"%}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.business %}
 {% endif %}

content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md

@@ -1,6 +1,6 @@
 ---
 title: Disabling and enabling a workflow
-intro: You can disable and re-enable a workflow using {% data variables.product.prodname_dotcom %} or the REST API.
+intro: 'You can disable and re-enable a workflow using {% data variables.product.prodname_dotcom %} or the REST API.'
 product: '{% data reusables.gated-features.actions %}'
 versions:
   free-pro-team: '*'

content/actions/managing-workflow-runs/removing-workflow-artifacts.md

@@ -39,4 +39,4 @@ You can also define a custom retention period for individual artifacts using the
 ### Finding the expiration date of an artifact
 
 You can use the API to confirm the date that an artifact is scheduled to be deleted. For more information, see the `expires_at` value returned by "[List artifacts for a repository](/rest/reference/actions#artifacts)."
-{% endif %}
+{% endif %}

content/actions/reference/workflow-syntax-for-github-actions.md

@@ -946,7 +946,7 @@ jobs:
 
 #### **`jobs.<job_id>.container.image`**
 
-The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "[email protected]" %}public{% endif %} registry name.
+The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "[email protected]" %}public{% endif %} registry name.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "[email protected]" %}
 #### **`jobs.<job_id>.container.credentials`**
@@ -1029,7 +1029,7 @@ services:
 
 #### **`jobs.<job_id>.services.<service_id>.image`**
 
-The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a {% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "[email protected]" %}public{% endif %} registry name.
+The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a {% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "[email protected]" %}public{% endif %} registry name.
 
 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "[email protected]" %}
 #### **`jobs.<job_id>.services.<service_id>.credentials`**

content/admin/installation/installing-github-enterprise-server-on-google-cloud-platform.md

@@ -25,7 +25,7 @@ Before launching {% data variables.product.product_location_enterprise %} on Goo
 #### Supported machine types
 
 {% data variables.product.prodname_ghe_server %} is supported on the following Google Compute Engine (GCE) machine types. For more information, see [the Google Cloud Platform machine types article](https://cloud.google.com/compute/docs/machine-types).
-{% if currentVersion != "free-pro-team@latest" %}
+
 | High-memory   |
   ------------- |
 | n1-highmem-4  |
@@ -34,7 +34,6 @@ Before launching {% data variables.product.product_location_enterprise %} on Goo
 | n1-highmem-32 |
 | n1-highmem-64 |
 | n1-highmem-96 |
-{% endif %}
 
 #### Recommended machine types
 

content/admin/user-management/requiring-two-factor-authentication-for-an-organization.md

@@ -11,7 +11,7 @@ When using LDAP or built-in authentication, two-factor authentication is support
 
 {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
 
-For more information, see [this chart on authentication methods that support 2FA](/enterprise/{{ currentVersion }}/user/articles/about-two-factor-authentication/#authentication-methods-that-support-2fa).
+For more information, see "[About two-factor authentication](/github/authenticating-to-github/about-two-factor-authentication)."
 
 ### Requirements for enforcing two-factor authentication