GitHub Actions 1 Flashcards
What is GitHub Actions?
A CI/CD and automation platform that allows you to build, test, and deploy code directly from GitHub.
What is a workflow in GitHub Actions?
A configuration file that defines automated processes in your repository, located in .github/workflows.
What is a job in GitHub Actions?
A set of steps that are executed as part of a workflow. Each job runs in its own virtual environment.
What are steps in GitHub Actions?
Individual tasks within a job, such as running a script or installing dependencies.
What does runs-on specify in a job configuration?
The virtual environment or runner where the job will execute (e.g., ubuntu-latest, windows-latest).
What is an action in GitHub Actions?
A reusable unit of code that performs a specific task, such as checking out code or setting up a programming environment.
What is the purpose of the on field in a workflow?
Specifies the events that trigger the workflow, such as push, pull_request, or schedule.
What is the difference between a custom action and a marketplace action?
Custom actions are created by you, while marketplace actions are pre-built by others and available for reuse.
What is a runner in GitHub Actions?
A server that runs workflows; GitHub provides hosted runners or you can set up self-hosted runners.
What is a matrix build in GitHub Actions?
A feature that allows testing across multiple configurations, like different versions of a language or operating system.
What is a secret in GitHub Actions?
Sensitive data (e.g., API keys, tokens) stored securely in a repository and accessed in workflows.
What is the GitHub Actions Marketplace?
A catalog of pre-built actions and workflows created by the community and GitHub.
What does uses do in a step?
Specifies an action from the marketplace or a repository to be used in the step.
What is caching in GitHub Actions?
Storing dependencies or build artifacts to speed up workflows using actions like actions/cache.
What is the jobs.<job_id>.needs field used for?</job_id>
To define job dependencies, ensuring that a job runs only after its dependencies have completed.