GitHub Pull Requests (PRs) - The Complete Guide

Master GitHub Pull Requests! Create, review, approve, and merge PRs like a professional developer!

Introduction

Pull Requests (PRs) are how teams collaborate on GitHub! Let's master them!

What You Will Learn

  • Creating a Pull Request
  • Writing great PR descriptions
  • Reviewing PRs
  • Approving and merging PRs

Prerequisites

What is a Pull Request?

A Pull Request is a request to merge your branch into another branch! It lets you:

  • Review code!
  • Discuss changes!
  • Run CI checks!
  • Merge safely!

How to Create a Pull Request!

  1. Push your branch to GitHub: 
    git push -u origin feature-login
  2. On GitHub, you'll see a "Compare & pull request" button! Click it!
  3. Fill in title and description!
  4. (Optional) Request reviewers!
  5. Click "Create pull request"!

Writing Great PR Descriptions!

Explain what and why!

  • What changed?
  • Why?
  • Screenshots if UI changed!
  • Link to issues!

Template example:

## Description
Brief description of the change

## Type of Change
- [ ] Bug fix
- [ ] New feature

## How to Test
Steps to test

## Screenshots (if applicable)

Reviewing PRs!

When reviewing:

  • Be kind!
  • Be specific!
  • Suggest improvements!
  • Approve when ready!

Merging a PR!

Once approved and all checks pass:

  1. Click "Merge pull request"!
  2. Confirm merge!
  3. Delete the branch! (Good practice!)

Best Practices!

  1. Small PRs: Easier to review!
  2. Clear title/description: Help reviewers!
  3. Link to issues: Context!
  4. Self-review first: Catch obvious issues!
  5. Respond to feedback: Collaborate!

Summary

Pull Requests are essential for team collaboration!

Related Articles

Previous Tutorial

← Merging

Next Tutorial

Let's learn open source! → Open Source Contributions

← Back to Syllabus