Skip to main content
Мы публикуем частые обновления нашей документации, и перевод этой страницы, возможно, еще выполняется. Актуальные сведения см. в документации на английском языке.
В настоящее время GitHub AE находится в ограниченном выпуске.

Using the latest version of the official bundled actions

Корпоративный экземпляр включает ряд встроенных действий, которые можно использовать в рабочих процессах.

Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "About using actions in your enterprise."

These bundled actions are a point-in-time snapshot of the official actions found at, so there may be newer versions of these actions available. You can use the actions-sync tool to update these actions, or you can configure GitHub Connect to allow access to the latest actions on These options are described in the following sections.

Using actions-sync to update the bundled actions

To update the bundled actions, you can use the actions-sync tool to update the snapshot. For more information on using actions-sync, see "Manually syncing actions from"

Using GitHub Connect to access the latest actions

You can use GitHub Connect to allow GitHub AE to use actions from For more information, see "Enabling automatic access to actions using GitHub Connect."

Once GitHub Connect is configured, you can use the latest version of an action by deleting its local repository in the actions organization on your instance. For example, if your enterprise instance is using v1 of the actions/checkout action, and you need to use actions/checkout@v3 which isn't available on your enterprise instance, perform the following steps to be able to use the latest checkout action from

  1. From an enterprise owner account on GitHub AE, navigate to the repository you want to delete from the actions organization (in this example checkout).

  2. By default, site administrators are not owners of the bundled actions organization. To get the access required to delete the checkout repository, you must use the site admin tools. Click in the upper-right corner of any page in that repository.

  3. Click Security to see the security overview for the repository.

    Screenshot of the site admin details for a repository. The "Security" link is highlighted with an orange outline.

  4. Under "Privileged access", click Unlock. Unlock button

  5. Under Reason, type a reason for unlocking the repository, then click Unlock. Confirmation dialog

  6. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the actions organization. At the top of the page, click the repository name, in this example checkout, to return to the summary page. Repository name link

  7. Under "Repository info", click View code to leave the site admin pages and display the checkout repository.

  8. Delete the checkout repository within the actions organization. For information on how to delete a repository, see "Deleting a repository." View code link

  9. Configure your workflow's YAML to use actions/checkout@v3.

  10. Each time your workflow runs, the runner will use the specified version of actions/checkout from

    Note: The first time the checkout action is used from, the actions/checkout namespace is automatically retired on your enterprise. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "Enabling automatic access to actions using GitHub Connect."