GitHub Actions — Workflow Vocabulary and Language
Learn the vocabulary of GitHub Actions: workflows, jobs, steps, runners, secrets, and matrix strategies.
0 / 22 completed
1 / 22
What is a 'workflow' in GitHub Actions?
A GitHub Actions workflow is a YAML configuration file in .github/workflows/ that defines automated processes (CI, CD, automation) triggered by events like push, pull_request, or schedule.
2 / 22
What is a 'runner' in GitHub Actions?
A runner is the compute environment where workflow jobs run. GitHub provides hosted runners (ubuntu-latest, windows-latest, macos-latest); teams can also configure self-hosted runners.
3 / 22
What is a 'matrix strategy' in GitHub Actions?
A matrix strategy defines variable combinations and runs the job once per combination — e.g., matrix: os: [ubuntu, windows], node: [16, 18, 20] creates 6 parallel job runs.
4 / 22
What is a 'composite action' in GitHub Actions?
A composite action packages multiple steps into a single reusable action — reducing duplication across workflows. Called with uses: ./path/to/action or a public action reference.
5 / 22
What does 'concurrency' control in GitHub Actions do?
concurrency groups prevent redundant runs — e.g., cancelling the previous push's CI run when a new push arrives on the same branch. Configured with concurrency: group: and cancel-in-progress: true.
6 / 22
Sarah: 'Hey team, I've added a new step to the PR workflow that runs tests and then deploys to staging. It's running automatically whenever someone pushes to the `develop` branch. Should we update the pull request description to include this?'
Which of the following best describes Sarah's action regarding the GitHub Actions workflow?Sarah is correctly identifying the addition of new steps within an existing workflow. The term 'steps' refers to individual tasks performed by a workflow – in this case, running tests and deploying. While 'triggers' initiate workflows, it's the *steps* that define what happens once the workflow starts; creating separate branches addresses environment isolation, and manually triggering is outside the scope of automated workflow management. This demonstrates an understanding of workflow components.7 / 22
David: 'I've just reviewed the PR and noticed the workflow is currently only running `npm install` which isn't sufficient to build the application before deployment. It needs a step that actually executes the build command. I've added a comment suggesting adding a 'Run Build' action after the `npm install` step, but I'm not sure how to formally request this change within GitHub Actions terminology.'Trigger in this context refers to what initiates a GitHub Actions workflow. David isn't asking for a new trigger; he's highlighting a missing step within the *existing* workflow. He correctly identifies that the build process needs to be included before deployment, and is requesting an action—specifically 'Run Build'—to achieve this. Option A is incorrect because it misinterprets branch triggers. Option C is partially correct but misses the key terminology around workflow steps.
8 / 22
Sarah has configured a GitHub Actions workflow for her project. The current workflow automatically runs `npm install` whenever code is pushed to the `develop` branch and then deploys to staging. After reviewing a pull request, David points out that this workflow doesn't include a build step before deployment. He suggests adding a 'Run Build' action after `npm install`. Which of the following best describes David's intention in this scenario?
Note: Consider the terminology used by GitHub Actions when requesting changes to a workflow.The correct answer is 2. David's intention is to *add* a new step—the 'Run Build' action—to the workflow. This clarifies that he wants to *trigger* this new action after `npm install` completes, not to modify the existing step itself. The other options misinterpret the request; a manual deployment isn't what David is proposing, and directly modifying the `npm install` step would bypass the need for a distinct build step which is generally considered best practice for maintainability and clarity.
9 / 22
Sarah: 'Hey team, I've added a new step to the PR workflow that runs tests and then deploys to staging. It's running automatically whenever someone pushes to the `develop` branch. Should we update the pull request description to include this?'
Which of the following best describes Sarah's action regarding the GitHub Actions workflow?Sarah is correctly identifying the addition of new steps within an existing workflow. The term 'steps' refers to individual tasks performed by a workflow – in this case, running tests and deploying. While 'triggers' initiate workflows, it's the *steps* that define what happens once the workflow starts; creating separate branches addresses environment isolation, and manually triggering is outside the scope of automated workflow management. This demonstrates an understanding of workflow components.10 / 22
David: 'I've just reviewed the PR and noticed the workflow is currently only running `npm install` which isn't sufficient to build the application before deployment. It needs a step that actually executes the build command. I've added a comment suggesting adding a 'Run Build' action after the `npm install` step, but I'm not sure how to formally request this change within GitHub Actions terminology.'Trigger in this context refers to what initiates a GitHub Actions workflow. David isn't asking for a new trigger; he's highlighting a missing step within the *existing* workflow. He correctly identifies that the build process needs to be included before deployment, and is requesting an action—specifically 'Run Build'—to achieve this. Option A is incorrect because it misinterprets branch triggers. Option C is partially correct but misses the key terminology around workflow steps.
11 / 22
Sarah has configured a GitHub Actions workflow for her project. The current workflow automatically runs `npm install` whenever code is pushed to the `develop` branch and then deploys to staging. After reviewing a pull request, David points out that this workflow doesn't include a build step before deployment. He suggests adding a 'Run Build' action after `npm install`. Which of the following best describes David's intention in this scenario?
Note: Consider the terminology used by GitHub Actions when requesting changes to a workflow.The correct answer is 2. David's intention is to *add* a new step—the 'Run Build' action—to the workflow. This clarifies that he wants to *trigger* this new action after `npm install` completes, not to modify the existing step itself. The other options misinterpret the request; a manual deployment isn't what David is proposing, and directly modifying the `npm install` step would bypass the need for a distinct build step which is generally considered best practice for maintainability and clarity.
12 / 22
Sarah: 'Hey team, I've added a new step to the PR workflow that runs tests and then deploys to staging. It's running automatically whenever someone pushes to the `develop` branch. Should we update the pull request description to include this?'
Which of the following best describes Sarah's action regarding the GitHub Actions workflow?Sarah is correctly identifying the addition of new steps within an existing workflow. The term 'steps' refers to individual tasks performed by a workflow – in this case, running tests and deploying. While 'triggers' initiate workflows, it's the *steps* that define what happens once the workflow starts; creating separate branches addresses environment isolation, and manually triggering is outside the scope of automated workflow management. This demonstrates an understanding of workflow components.13 / 22
David: 'I've just reviewed the PR and noticed the workflow is currently only running `npm install` which isn't sufficient to build the application before deployment. It needs a step that actually executes the build command. I've added a comment suggesting adding a 'Run Build' action after the `npm install` step, but I'm not sure how to formally request this change within GitHub Actions terminology.'Trigger in this context refers to what initiates a GitHub Actions workflow. David isn't asking for a new trigger; he's highlighting a missing step within the *existing* workflow. He correctly identifies that the build process needs to be included before deployment, and is requesting an action—specifically 'Run Build'—to achieve this. Option A is incorrect because it misinterprets branch triggers. Option C is partially correct but misses the key terminology around workflow steps.
14 / 22
Sarah has configured a GitHub Actions workflow for her project. The current workflow automatically runs `npm install` whenever code is pushed to the `develop` branch and then deploys to staging. After reviewing a pull request, David points out that this workflow doesn't include a build step before deployment. He suggests adding a 'Run Build' action after `npm install`. Which of the following best describes David's intention in this scenario?
Note: Consider the terminology used by GitHub Actions when requesting changes to a workflow.The correct answer is 2. David's intention is to *add* a new step—the 'Run Build' action—to the workflow. This clarifies that he wants to *trigger* this new action after `npm install` completes, not to modify the existing step itself. The other options misinterpret the request; a manual deployment isn't what David is proposing, and directly modifying the `npm install` step would bypass the need for a distinct build step which is generally considered best practice for maintainability and clarity.
15 / 22
Sarah: 'Hey team, I've added a new step to the PR workflow that runs tests and then deploys to staging. It's running automatically whenever someone pushes to the `develop` branch. Should we update the pull request description to include this?'
Which of the following best describes Sarah's action regarding the GitHub Actions workflow?Sarah is correctly identifying the addition of new steps within an existing workflow. The term 'steps' refers to individual tasks performed by a workflow – in this case, running tests and deploying. While 'triggers' initiate workflows, it's the *steps* that define what happens once the workflow starts; creating separate branches addresses environment isolation, and manually triggering is outside the scope of automated workflow management. This demonstrates an understanding of workflow components.16 / 22
David: 'I've just reviewed the PR and noticed the workflow is currently only running `npm install` which isn't sufficient to build the application before deployment. It needs a step that actually executes the build command. I've added a comment suggesting adding a 'Run Build' action after the `npm install` step, but I'm not sure how to formally request this change within GitHub Actions terminology.'Trigger in this context refers to what initiates a GitHub Actions workflow. David isn't asking for a new trigger; he's highlighting a missing step within the *existing* workflow. He correctly identifies that the build process needs to be included before deployment, and is requesting an action—specifically 'Run Build'—to achieve this. Option A is incorrect because it misinterprets branch triggers. Option C is partially correct but misses the key terminology around workflow steps.
17 / 22
Sarah has configured a GitHub Actions workflow for her project. The current workflow automatically runs `npm install` whenever code is pushed to the `develop` branch and then deploys to staging. After reviewing a pull request, David points out that this workflow doesn't include a build step before deployment. He suggests adding a 'Run Build' action after `npm install`. Which of the following best describes David's intention in this scenario?
Note: Consider the terminology used by GitHub Actions when requesting changes to a workflow.The correct answer is 2. David's intention is to *add* a new step—the 'Run Build' action—to the workflow. This clarifies that he wants to *trigger* this new action after `npm install` completes, not to modify the existing step itself. The other options misinterpret the request; a manual deployment isn't what David is proposing, and directly modifying the `npm install` step would bypass the need for a distinct build step which is generally considered best practice for maintainability and clarity.
18 / 22
Mark received the following Slack message from a teammate: 'Hey, I've been experimenting with GitHub Actions and added a step to our workflow that uses a 'matrix strategy' to run tests across different Node.js versions. It's configured to automatically deploy to staging whenever code is pushed to the `develop` branch.' What does Mark understand about this configuration?
A 'matrix strategy' in GitHub Actions allows you to run multiple steps concurrently with different configurations – like different Node.js versions or operating systems. This is useful for testing compatibility across various environments without needing separate workflows. Mark correctly understands that the configuration enables parallel execution of tests, which is a key benefit.
19 / 22
During a standup meeting, Liam says: 'I've added a new workflow step that uses a 'composite action' to handle the deployment process. It combines several smaller actions into one logical unit.' What is the primary purpose of using a composite action in this scenario?
A 'composite action' is a way to logically group multiple GitHub Actions into a single unit. This simplifies workflow management by providing a higher-level abstraction and reducing the need for complex nested workflows. Liam's statement correctly identifies the core benefit: streamlining deployment processes.
20 / 22
You're reviewing a PR description for a GitHub Actions workflow that automatically deploys to production. The description includes the following: 'The workflow uses concurrency controls to ensure deployments are fast and reliable.' What does 'concurrency' control in this context refer to?
'Concurrency' in GitHub Actions means allowing multiple workflow steps to run simultaneously. This dramatically reduces deployment times by leveraging available resources effectively – a key factor in achieving fast and reliable deployments as described in the PR description.
21 / 22
Elena is explaining her GitHub Actions workflow to a junior developer: 'I've configured this workflow to automatically run `npm install` whenever code is pushed to the `develop` branch and then deploy to staging.' The junior developer asks: 'But shouldn't it also build the application before deploying?' What is Elena implicitly suggesting?
Elena's statement implicitly highlights the importance of including a build step *before* deployment. Simply installing dependencies (`npm install`) isn't enough; the code needs to be compiled and packaged into an executable form before it can be deployed to staging. This is a common best practice.
22 / 22
You receive this API response from GitHub Actions: { 'status': 'running', 'workflow_run.id': 'a1b2c3d4e5f6g7h8i9j0', 'workflow_runs.url': 'https://api.github.com/repos/your-org/your-repo/runs/a1b2c3d4e5f6g7h8i9j0' } What does this API response primarily indicate?
This API response from GitHub Actions indicates that a workflow run is currently in progress. The 'status' field confirms this and provides information like the workflow's ID and a link to its details – allowing you to monitor its execution.
Frequently Asked Questions
What will I practise in "GitHub Actions — Workflow Vocabulary and Language"?
Learn the vocabulary of GitHub Actions: workflows, jobs, steps, runners, secrets, and matrix strategies.
How many exercises are in this module?
This module has 22 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more GitHub Platform Language exercises?
Browse the full GitHub Platform Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.