Note
GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
This version of GitHub Enterprise Server was discontinued on 2024-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.
You can create your own actions, use and customize actions shared by the GitHub community, or write and share the actions you build.
Note
GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap.
Actions are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the GitHub community.
This guide shows you the minimal steps required to build a Docker container action.
In this guide, you'll learn how to build a JavaScript action using the actions toolkit.
In this guide, you'll learn how to build a composite action.
You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
When creating a Dockerfile
for a Docker container action, you should be aware of how some Docker instructions interact with GitHub Actions and an action's metadata file.
You can use exit codes to set the status of an action. GitHub displays statuses to indicate passing or failing actions.
You can leverage automation and open source best practices to release and maintain actions.