ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。

Using the latest version of the official bundled actions

You can update the actions that are bundled with your GitHub Enterprise Server instance, or use actions directly from GitHub.com.

ここには以下の内容があります:

ノート: GitHubホストランナーは、現在GitHub Enterprise Serverでサポートされていません。 GitHub public roadmapで、計画されている将来のサポートに関する詳しい情報を見ることができます。

Your GitHub Enterprise Server instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "Official actions bundled with GitHub Enterprise Server".

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 GitHub.com.

Alternatively, if your GitHub Enterprise Server instance has GitHub Connect enabled, then you have additional options for using the latest actions from GitHub.com:

  • Your workflow file can directly reference a specific tag that only exists on GitHub.com.
  • To force the workflow file to use the actions on GitHub.com, you can edit the tag assigned to the bundled actions.

These options are described in more detail in the following sections.

Using actions-sync to update a bundled action

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

Using actions from GitHub.com

Once configured, you can use a new version of an action from GitHub.com by manually specifying the required version in the workflow file. For example, to use version v2.2.1 of actions/setup-python from GitHub.com, 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

If you remove the version tag that was previously assigned to an action, GitHub Enterprise Server will check GitHub.com for the required tag. For more information on working with tags, see "Viewing tags."

For example, to use version v2.2.1 of actions/setup-python from GitHub.com:

  1. In GitHub Enterprise Server, delete the v2 tag from the actions/setup-python repository.
  2. Create a workflow that uses actions/setup-python with the v2 tag.

When the workflow is unable to find the specified v2 tag on GitHub Enterprise Server, it checks GitHub.com for the required tag. If it finds a tagged version of that action, GitHub Enterprise Server uses the version from GitHub.com.

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

OR, learn how to contribute.