GitHub Professional Certificate GitHub Projects and Issue Management 2 — Questions and Answers
Question 1: In GitHub Projects (Projects v2), what are 'custom fields' used for?
- Adding custom webhooks to a project
- Extending project items with additional metadata like priority, story points, or dates (Correct answer)
- Creating custom branch naming rules
- Defining custom deployment environments
Correct answer: Extending project items with additional metadata like priority, story points, or dates
Custom fields in GitHub Projects v2 let teams add metadata such as priority, effort estimates, or iteration numbers directly to project items.
Question 2: What is the difference between a repository-level project and an organization-level project in GitHub?
- Repository projects can include issues from multiple repos; organization projects cannot
- Organization projects can aggregate issues and PRs from multiple repositories; repository projects are limited to one repo (Correct answer)
- Organization projects require a paid plan; repository projects are always free
- There is no functional difference between the two
Correct answer: Organization projects can aggregate issues and PRs from multiple repositories; repository projects are limited to one repo
Organization-level projects can pull in issues and pull requests from any repository within the organization, enabling cross-repo tracking.
Question 3: Which GitHub Projects view is best suited for long-term planning and showing item timelines?
- Board view
- Table view
- Roadmap view (Correct answer)
- List view
Correct answer: Roadmap view
The Roadmap view in GitHub Projects displays items on a timeline, making it ideal for visualizing long-term plans and scheduling.
Question 4: What is the purpose of GitHub Issue Templates?
- To pre-fill issue forms with structured prompts that guide reporters in providing necessary information (Correct answer)
- To automatically close issues after a set time period
- To restrict which users can open issues in a repository
- To convert issues into pull requests automatically
Correct answer: To pre-fill issue forms with structured prompts that guide reporters in providing necessary information
Issue templates provide structured forms or markdown starters that prompt reporters to include all relevant information such as steps to reproduce, expected behavior, and environment details.
Question 5: How does the 'Duplicate' label or closing-as-duplicate workflow help in GitHub issue management?
- It merges two issues into one automatically
- It signals that an issue has already been reported and links to the original, reducing redundant work (Correct answer)
- It assigns the duplicate issue to the same person as the original
- It automatically copies all comments from one issue to another
Correct answer: It signals that an issue has already been reported and links to the original, reducing redundant work
Marking an issue as a duplicate and referencing the original prevents teams from working on the same problem twice and consolidates discussion.
Question 6: What is a GitHub Project's 'Iteration' field used for?
- Counting the number of times an issue has been reopened
- Grouping work into fixed time periods (sprints) for agile planning (Correct answer)
- Tracking the version of the codebase associated with an issue
- Scheduling automated reminders for issue assignees
Correct answer: Grouping work into fixed time periods (sprints) for agile planning
The Iteration field in GitHub Projects lets teams assign items to specific sprints or time-boxed cycles, enabling agile-style sprint planning and tracking.
GitHub Professional Certificate GitHub Projects and Issue Management 2
In GitHub Projects (Projects v2), what are 'custom fields' used for?