GitHub Projects — Vocabulary
Learn vocabulary for GitHub Projects: project boards, milestones, labels, closing issues via PRs, roadmap views, and issue triage.
0 / 45 completed
1 / 45
What is a 'milestone' in GitHub, and how is it used?
Milestones in GitHub group issues and PRs toward a shared goal — such as a version release or a quarterly objective. They show progress (e.g., '8 of 12 issues closed') and a target date, making them useful for sprint or release planning.
2 / 45
What does the phrase 'closes #123' in a pull request description do?
GitHub recognises closing keywords (closes, fixes, resolves) followed by an issue number in PR descriptions. On merge, the referenced issue is automatically closed and the PR is linked to the issue, providing full traceability.
3 / 45
What is 'issue triage' in a GitHub project workflow?
Triage is the intake process for issues: a maintainer or rotation team reviews new issues to confirm they are valid, add context labels, assign to a milestone or project board column, and set priority — ensuring the backlog stays organised and actionable.
4 / 45
What is a 'label taxonomy' in GitHub project management?
A label taxonomy is a deliberate system — teams define categories and conventions upfront so labels are applied consistently. Without this structure, labels proliferate inconsistently and lose their filtering value. Good taxonomies separate type, priority, and status concerns.
5 / 45
What is the 'roadmap view' in GitHub Projects (Projects v2)?
GitHub Projects v2 includes a roadmap (timeline) view that lets teams see work items plotted on a calendar, set date fields, and visualise dependencies across sprints and quarters — useful for communicating delivery plans to stakeholders.
6 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
7 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
8 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
9 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.10 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
11 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
12 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
13 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
14 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.15 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
16 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
17 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
18 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
19 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.20 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
21 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
22 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
23 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
24 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.25 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
26 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
27 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
28 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
29 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.30 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
31 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
32 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
33 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
34 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.35 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
36 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
37 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
38 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
39 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.40 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
41 / 45
Sarah: "Hey team, I've just created a new project called 'Phoenix'. It has three columns: 'Backlog', 'In Progress', and 'Done'. I'm using it to track the development of our new API. Mark comments on her PR: 'This looks good, but can you add a label for 'API v2'?'. What does Mark likely mean when he suggests adding a label?Labels in GitHub Projects are crucial for categorization and filtering. They allow you to group issues and pull requests based on criteria like feature type (e.g., 'API v2'), severity, or assignee. By suggesting a label, Mark is requesting that the PR be associated with this specific category, which will improve organization and make it easier to find related work within the project. Options A and B are incorrect because they relate to column structure or task priority, not labels.
42 / 45
David in the standup update says: "We're focusing on completing the user authentication flow this sprint. The 'authentication' task is currently in the 'In Progress' column of the 'Phoenix' project." Maria replies via Slack: "Are we using labels to categorize tasks within that project?" What does Maria likely want to know about David's update?Maria's question probes whether David is utilizing GitHub Project's features for task management. Labels are a key way to categorize and prioritize work within a project column, directly connecting the 'authentication' task to its broader context. Options A, C, and D refer to different aspects of Agile estimation or API versions – they aren't related to the core function of using GitHub Projects to organize tasks by label.
43 / 45
John wrote a PR titled 'Implement User Profile Updates'. The PR description reads: 'Fixes #456. Resolves user profile data inconsistencies reported in the recent API response. Added a new label: `profile-update`.' Alice, during code review, comments: 'The label seems appropriate, but are we tracking the specific API endpoint this change affects?' What is Alice's primary concern?Alice's question highlights the importance of granular labeling within GitHub Projects. While labels like `profile-update` are useful for broad categorization, she's specifically asking if a more detailed label (perhaps referencing an API endpoint) is being used to track the change's impact and facilitate debugging or future updates. This demonstrates an understanding that labels can be layered for different levels of detail – a common practice in project management.
44 / 45
Mark comments on a pull request: 'This looks good, but can you add a label for 'API v2'?'. Within the context of a GitHub project using Kanban boards and labels, what is Mark most likely requesting?
Mark is suggesting a label to improve organization and filtering of tasks. Labels in GitHub Projects provide a way to categorize issues and pull requests, allowing for more efficient tracking and reporting— specifically, grouping related work by API version. The other options are less relevant to the immediate request for adding a label for 'API v2', which directly relates to task categorization.45 / 45
The team is using GitHub Projects to manage the development of a new feature called 'Nova'. During a code review, Liam says: 'I'm not seeing any labels on this PR. Should we add one to indicate it's related to the Nova project?' Chloe responds with: 'I think so. Let's add `nova-feature`.' What is the *primary* reason Chloe suggests adding a label in this situation?
Chloe is suggesting adding a label because labels provide a way to categorize and group issues and pull requests within a GitHub project. This allows the team to quickly identify all PRs related to 'Nova', making it easier to track progress, manage dependencies, and ensure that changes are properly associated with the feature. Adding the `nova-feature` label directly addresses this need for categorization and improves visibility.
Frequently Asked Questions
What will I practise in "GitHub Projects — Vocabulary"?
Learn vocabulary for GitHub Projects: project boards, milestones, labels, closing issues via PRs, roadmap views, and issue triage.
How many exercises are in this module?
This module has 45 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.