GitHub Actions and Workflow Automation Flashcards

What is GitHub Actions primarily used for?

Answer: Automating code workflows

GitHub Actions is primarily used for automating various code-related workflows, such as continuous integration (CI), continuous delivery (CD), and other custom tasks. It allows developers to define automated processes that run in response to GitHub events, streamlining development cycles and improving efficiency. This reduces manual effort and speeds up releases.

Which file defines a GitHub Actions workflow?

Answer: .github/workflows/*.yml

GitHub Actions workflows are defined in YAML files located within the `.github/workflows/` directory in your repository. These YAML files specify the events that trigger the workflow, the jobs to be executed, and the steps within each job. This structured format clearly outlines the automated process for your project.

What triggers a GitHub Actions workflow?

Answer: GitHub events like push or PR

GitHub Actions workflows are triggered by specific events that occur in your repository, such as a `push` to a branch, the opening or updating of a `pull_request`, or even scheduled `cron` jobs. These event-driven triggers allow for highly flexible and automated CI/CD pipelines. This ensures workflows run exactly when needed.

What is a 'job' in GitHub Actions?

Answer: A unit of steps within a workflow

In GitHub Actions, a 'job' is a set of steps that execute on the same runner, which is a virtual machine or container. Workflows can contain one or more jobs, which can run sequentially or in parallel. This allows for organized execution of tasks like building, testing, and deploying your code.

Which virtual environments can GitHub Actions use?

Answer: macOS, Windows, and Ubuntu

GitHub Actions provides a variety of virtual environments, known as runners, to execute your workflows. These include popular operating systems like Ubuntu (Linux), Windows, and macOS. This flexibility allows you to test and build your applications across different platforms, ensuring compatibility and broad coverage.

What is the purpose of a 'step' in a GitHub Action job?

Answer: To execute a command or action

A 'step' in a GitHub Actions job represents a single task that is executed as part of the workflow. Each step can either run a shell command directly or execute a predefined 'action' (a reusable piece of code). This allows for granular control over the workflow's operations, enabling precise automation of tasks.