GitHub Professional Certificate GitHub Projects and Issue Management 1 — Questions and Answers
Question 1: What is the primary purpose of GitHub Issues?
- To store binary release artifacts
- To track bugs, feature requests, tasks, and other work items for a project (Correct answer)
- To manage repository access permissions
- To configure CI/CD pipelines
Correct answer: To track bugs, feature requests, tasks, and other work items for a project
GitHub Issues provide a built-in issue tracking system where teams can log bugs, feature requests, and tasks and discuss them collaboratively.
Question 2: What is a GitHub Milestone used for?
- Marking a specific commit as a release candidate
- Grouping related issues and pull requests to track progress toward a goal or deadline (Correct answer)
- Setting required status checks on branches
- Flagging security vulnerabilities in dependencies
Correct answer: Grouping related issues and pull requests to track progress toward a goal or deadline
Milestones group issues and pull requests under a common goal with an optional due date so teams can track overall progress.
Question 3: Which GitHub feature allows teams to organize issues and pull requests into a Kanban-style board?
- GitHub Discussions
- GitHub Projects (Correct answer)
- GitHub Wikis
- GitHub Releases
Correct answer: GitHub Projects
GitHub Projects provides flexible boards (table, board, and roadmap views) to organize and track issues and pull requests across a project.
Question 4: What is the function of Labels in GitHub Issues?
- To assign a dollar value to each issue
- To categorize and filter issues and pull requests by type, priority, or status (Correct answer)
- To restrict who can comment on an issue
- To link issues to a deployment environment
Correct answer: To categorize and filter issues and pull requests by type, priority, or status
Labels are colored tags applied to issues and pull requests to categorize them (e.g., bug, enhancement, good first issue) and enable easy filtering.
Question 5: How can you close a GitHub Issue automatically when a pull request is merged?
- By adding the issue number to the branch name
- By using closing keywords like 'Closes #123' in the pull request description (Correct answer)
- By assigning the issue to the PR author
- By adding a 'ready to merge' label to the issue
Correct answer: By using closing keywords like 'Closes #123' in the pull request description
Using closing keywords such as 'Closes', 'Fixes', or 'Resolves' followed by the issue number in a PR description automatically closes the linked issue when the PR is merged.
Question 6: What does 'assigning' a GitHub Issue to a user indicate?
- The user has administrative control over the issue's lifecycle
- The user is responsible for addressing or working on that issue (Correct answer)
- The issue is blocked until that user approves it
- The user will be billed for the issue's resolution time
Correct answer: The user is responsible for addressing or working on that issue
Assigning an issue designates a specific contributor as the person responsible for working on or resolving that issue.
GitHub Professional Certificate GitHub Projects and Issue Management 1
What is the primary purpose of GitHub Issues?