Update description of how GHES can use the latest Actions (github#18723)

Martin Lopes · cschleiden · web-flow · commit 97bd9d2e1f63 · 2021-04-15T00:14:10.000Z
* Removed option about removing an action's tag

* Empty commit for CI

* Apply suggestions from code review

Co-authored-by: Christopher Schleiden &lt;cschleiden@github.com&gt;

Co-authored-by: Christopher Schleiden &lt;cschleiden@github.com&gt;
diff --git a/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md b/content/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions.md
@@ -14,10 +14,6 @@ Your {% data variables.product.prodname_ghe_server %} instance includes a number
 
 These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
 
-Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
-
-- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
-- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
 
 These options are described in more detail in the following sections.
 
@@ -30,16 +26,3 @@ To update the bundled actions, you can use the `actions-sync` tool to synchroniz
 {% data reusables.github-actions.actions-github-connect-requirement %}
 
 Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
-
-### Using the latest version by removing the specific action's tag
-
-{% data reusables.github-actions.actions-github-connect-requirement %}
-
-If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
-
-For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
-
-1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
-1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
-
-When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.
