GitHub Issues
📌 Covered in this chapter:
Bug Reports · Feature Requests · Labels · Assignees · Milestones · Issue Templates
Track bugs, feature requests, and tasks using GitHub Issues — labels, assignees, milestones, and templates.
1GitHub Issues — What You'll Learn
Track bugs, feature requests, and tasks using GitHub Issues — labels, assignees, milestones, and templates.
Here's everything this chapter covers, in the order you'll learn it:
- What a GitHub issue is
- Filing a bug report
- Filing a feature request
- Creating a general task issue
- Writing a clear issue title
- Writing a useful issue description
- Adding labels to categorize issues
- Assigning issues to team members
- Grouping issues into milestones
- Using issue templates for consistency
- Linking commits and PRs to an issue
- Closing issues automatically via commit messages
2Best Practices & Common Pitfalls
💡 Key things to remember:
- You can automatically close an issue when a pull request is merged by including 'Closes #12' (using the issue number) in the PR description or a commit message.
❓ Frequently Asked Questions (FAQ)
Q What's the most important thing to understand about github issues?
Focus on: Bug Reports · Feature Requests · Labels · Assignees · Milestones · Issue Templates. These are the core building blocks this chapter's examples are built around, and they show up repeatedly in later chapters of this course.
Q Is github issues something I'll use often in real projects?
Yes — every concept in this chapter reflects a real, everyday part of professional Git and GitHub workflows, not just a theoretical exercise.