Actions for Git and GitHubs
GitHub Actions is GitHub's built-in automation platform. A workflow file in .github/workflows runs jobs on events such as a push or pull request, executing steps on hosted runners to test, build or deploy. Releases and packages publish tagged versions and artifacts from the same repository.
Stage: Automation · Part of the Git and GitHub roadmap · Last reviewed 19 November 2026
What to learn in Actions
- Write a workflow that runs tests on every pull request
- Use secrets and environment variables in a job safely
- Cache dependencies to shorten workflow runs
- Create a tagged release with generated notes
- Publish a package from a workflow
Actions interview questions
What triggers a GitHub Actions workflow?
Workflows start from events declared under the on key, such as push, pull_request, schedule with cron syntax, workflow_dispatch for manual runs, or release. You can filter by branch, tag or file path to control when they run.
How should secrets be used in workflows?
Store them in repository or environment secrets and reference them with the secrets context, so they are masked in logs and not in code. Be careful with pull requests from forks, which do not receive secrets by default.
Where Actions fits in the Git and GitHub roadmap
Actions belongs to the Automation stage (intermediate level). CI on GitHub.
Back to the full Git and GitHub roadmap