Hack week 2025: remove unneeded FBV instances (14) - Actions (#53983)

Co-authored-by: Felicity Chapman <[email protected]>

Author: mchammer01

content/actions/administering-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md

@@ -19,15 +19,15 @@ type: how_to
 
 If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization.
 
-## Sharing {% ifversion internal-actions %}actions and {% endif %}workflows
+## Sharing {% ifversion ghec or ghes %}actions and {% endif %}workflows
 
-{% ifversion internal-actions %}
+{% ifversion ghec or ghes %}
 You can share both individual actions and entire workflows with your organization, with or without publishing the actions or workflows publicly. You can reuse actions and workflows exactly by referencing them in your workflow file, and you can create workflow templates.
 {% else %}
 Your organization can share workflows by reusing the workflows exactly or by creating workflow templates
 {% endif %}
 
-{% ifversion internal-actions %}
+{% ifversion ghec or ghes %}
 
 ### Sharing actions with your enterprise
 

content/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions.md

@@ -208,7 +208,7 @@ The same principles described above for using third-party actions also apply to
 
 {% data reusables.actions.dependabot-version-updates-for-actions %}
 
-{% ifversion internal-actions %}
+{% ifversion ghec or ghes %}
 
 ## Allowing workflows to access internal and private repositories
 

content/actions/sharing-automations/creating-actions/about-custom-actions.md

@@ -25,7 +25,7 @@ topics:
 You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.prodname_dotcom %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
 
 {% ifversion fpt or ghec %}
-You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built with everyone, your repository must be public. {% ifversion internal-actions %}To share actions only within your enterprise, your repository must be internal.{% endif %}
+You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built with everyone, your repository must be public. {% ifversion ghec %}To share actions only within your enterprise, your repository must be internal.{% endif %}
 {% endif %}
 
 Actions can run directly on a machine or in a Docker container. You can define an action's inputs, outputs, and environment variables.

content/actions/sharing-automations/reusing-workflows.md

@@ -60,7 +60,7 @@ A reusable workflow can be used by another workflow if any of the following is t
   You cannot directly use reusable workflows defined on {% data variables.product.prodname_dotcom_the_website %}. Instead store a copy of the reusable workflow on {% data variables.location.product_location %}, and call the workflow from that path.
 
   {% elsif actions-workflow-policy %}, and your {% ifversion ghec %}enterprise{% else %}organization{% endif %} allows you to use public reusable workflows.{% endif %}{% ifversion ghes or ghec %}
-* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion internal-actions %}[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}[AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}.{% endif %}
+* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise).{% endif %}
 * The called workflow is stored in a private repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion ghes or ghec %}[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise).{% else %}[AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-organization) and [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-from-your-private-repository).{% endif %}
 
 The following table shows the accessibility of reusable workflows to a caller workflow, depending on the visibility of the host repository.

content/actions/sharing-automations/sharing-actions-and-workflows-with-your-enterprise.md

@@ -2,7 +2,8 @@
 title: Sharing actions and workflows with your enterprise
 intro: You can share an action or reusable workflow with your enterprise without publishing the action or workflow publicly.
 versions:
-  feature: internal-actions
+  ghec: '*'
+  ghes: '*'
 type: tutorial
 topics:
   - Actions

content/actions/sharing-automations/sharing-actions-and-workflows-with-your-organization.md

@@ -12,7 +12,7 @@ redirect_from:
   - /actions/creating-actions/sharing-actions-and-workflows-with-your-organization
 ---
 
-## About {% data variables.product.prodname_actions %} access to private {% ifversion internal-actions %} or internal {% endif %}repositories
+## About {% data variables.product.prodname_actions %} access to private {% ifversion ghec or ghes %} or internal {% endif %}repositories
 
 You can share actions and reusable workflows within your organization, without publishing them publicly, by allowing {% data variables.product.prodname_actions %} workflows to access a private repository that contains the action or reusable workflow.
 
@@ -24,7 +24,7 @@ Any actions or reusable workflows stored in the private repository can be used i
 
 ## Sharing actions and workflows with your organization
 
-1. Store the action or reusable workflow in a private {% ifversion internal-actions %} or internal {% endif %}repository. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+1. Store the action or reusable workflow in a private {% ifversion ghec or ghes %} or internal {% endif %}repository. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
 1. Configure the repository to allow access to workflows in other private repositories. For more information, see [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-a-private-repository).
 
 ## Further reading

content/actions/writing-workflows/choosing-what-your-workflow-does/using-pre-written-building-blocks-in-your-workflow.md

@@ -33,7 +33,7 @@ Actions can be:
 
 The actions you use in your workflow can be defined in:
 
-* The same repository as your workflow file{% ifversion internal-actions %}
+* The same repository as your workflow file{% ifversion ghec or ghes %}
 * An internal repository within the same enterprise account that is configured to allow access to workflows{% endif %}
 * Any public repository
 * A published Docker container image on Docker Hub
@@ -91,7 +91,7 @@ The `action.yml` file is used to provide metadata for the action. Learn about th
 
 If an action is defined in a different repository than your workflow file, you can reference the action with the `{owner}/{repo}@{ref}` syntax in your workflow file.
 
-The action must be stored in a public repository{% ifversion internal-actions %} or an internal repository that is configured to allow access to workflows. For more information, see [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise).{% else %}.{% endif %}
+The action must be stored in a public repository{% ifversion ghec or ghes %} or an internal repository that is configured to allow access to workflows. For more information, see [AUTOTITLE](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise).{% else %}.{% endif %}
 
 ```yaml
 jobs:

content/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md

@@ -75,10 +75,6 @@ With reusable workflows, your team can call one workflow from another workflow,
 
 To provide a starting place for developers building new workflows, you can use workflow templates. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see [AUTOTITLE](/actions/using-workflows/creating-starter-workflows-for-your-organization).
 
-{% ifversion not internal-actions %}
-Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see [AUTOTITLE](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action).
-{% endif %}
-
 ## Managing resources
 
 You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.