GitHub Issues and Pull Requests: How to Use Them

What Are Issues?

Issues are used for bug reports, feature requests, and task tracking.

Create an Issue

1. Open the repository on GitHub
2. “Issues” tab → “New issue”
3. Enter a title and description → “Submit new issue”

Useful Issue Template

## Problem
What is happening?

## Steps to Reproduce
1.
2.
3.

## Expected Behavior
What should happen?

## Environment
- OS:
- Version:

What Are Pull Requests?

Pull Requests let you propose code changes and get them reviewed before merging.

Pull Request Workflow

# 1. Create a branch
git switch -c feature/fix-bug

# 2. Make changes and commit
git add .
git commit -m "fix: resolve the bug"

# 3. Push to GitHub
git push -u origin feature/fix-bug

4. Create a Pull Request on GitHub
5. Request a review
6. Merge after approval

Link a PR to an Issue

Adding these keywords to the PR body automatically closes the linked issue on merge:

fix #123
closes #123
resolves #123

Common Pitfalls

• Avoid pushing directly to main without a review
• Use descriptive branch names that convey the purpose
• Issue numbers can be auto-linked to PRs

Before opening a PR, consider cleaning up commits with git rebase Basics to make the diff easier to review.

Related Posts

• How to Push Your First Repository to GitHub
• Git Branch Basics: Create and Switch Branches
• GitHub Actions: Basic Auto-Deploy Setup
• Generate an SSH Key and Add It to GitHub

Recommended Services

• Fiverr - Find freelance developers and tech experts