Custom Actions for GitHub Actionss
Custom actions are reusable units of automation you build yourself. An action is defined by an action.yml metadata file and implemented as a JavaScript or TypeScript action, a Docker container action, or a composite action. You publish it from a repository so workflows can reference it by owner, name and version.
Stage: Reuse and Extension · Part of the GitHub Actions roadmap · Last reviewed 19 November 2026
What to learn in Custom Actions
- Write an action.yml with inputs, outputs and a runs section
- Build a JavaScript action using the actions toolkit
- Package a Docker container action with an entrypoint
- Tag releases with semantic versions and a movable major tag
- Test an action locally and in a sample workflow
Custom Actions interview questions
What are the three kinds of custom action?
JavaScript actions run directly on the runner using Node, so they start fast and work on all platforms. Docker container actions run in a container for a controlled environment on Linux runners. Composite actions combine other steps and actions in YAML.
Why version an action with tags like v1?
Consumers reference an action with a ref such as owner/action@v1. A major tag that you move forward with compatible updates lets them receive fixes automatically, while full version tags and commit SHAs give exact, reproducible pinning.
Where Custom Actions fits in the GitHub Actions roadmap
Custom Actions belongs to the Reuse and Extension stage (beginner level). Scale your automation.
Other units in this stage
Back to the full GitHub Actions roadmap