Frontend Academy · Lesson

Pull Request Workflow on GitHub

Open a pull request on GitHub, write a helpful description, respond to code review comments, and merge when approved.

Pull Request Workflow on GitHub is a free Frontend Academy lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Frontend Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What Is a Pull Request?

A Pull Request (PR) is a proposal to merge one branch into another. On GitHub, it creates a discussion thread where teammates review the code, leave comments, request changes, and ultimately approve the merge.

Creating a PR on GitHub

After pushing a feature branch to GitHub, a yellow banner appears offering to compare and create a PR. Click it, or go to Pull Requests → New pull request and select your branches.

Writing a Good PR Description

A good PR description explains: what changed and why. Include a screenshot for UI changes. Link the related issue. Describe how you tested it. The reader shouldn't need to read the code to understand the intent.

## Summary
Adds dark mode support using CSS custom properties.

## Why
Users requested dark mode (#123). Reduces eye strain for evening use.

## Testing
- Toggled dark/light mode on macOS and Windows
- Verified `prefers-color-scheme: dark` auto-triggers
- Tested with a screen reader (macOS VoiceOver)

Requesting Reviewers

Assign specific teammates as reviewers. They receive a notification and can approve, request changes, or comment. Most teams require at least one approval before merging.

Reading Code Review Comments

Comments appear inline on changed lines. Reviewers can: ask for clarification, suggest a different approach, or approve. Respond to each comment — either with a code change or a reason for not changing.

Responding to Requested Changes

When a reviewer requests changes, push new commits to the same branch. The PR updates automatically. Resolve each conversation by clicking 'Resolve conversation' after addressing it.

Draft PRs

Open a PR as a Draft to signal that it's work in progress. Draft PRs still allow review and discussion but can't be accidentally merged. Convert to Ready when it's complete.

Keeping Your Branch Up to Date

When main advances during review, rebase your branch on the latest main to avoid conflicts and ensure your changes work with new code.

git fetch origin
git rebase origin/main
git push --force-with-lease origin feature/dark-mode

Squash Merge vs Merge Commit vs Rebase

GitHub offers three merge strategies: Merge commit (preserves all commits), Squash and merge (one commit per PR, clean main history), Rebase and merge (linear, no merge commit). Teams usually choose one strategy for consistency.

Branch Protection Rules

Protect main by requiring PR review, requiring status checks to pass (CI), and prohibiting direct pushes. Set in GitHub → Settings → Branches.

PR Etiquette

Keep PRs small and focused. One PR per feature or fix. Large PRs are hard to review. Respond to review comments within a day. Thank reviewers. Be kind — code review is a teaching opportunity, not an audit.

Quick Check

What should a good PR description include?

Recap: Pull Request Workflow

Push feature branch → open PR with a clear description → request reviewers → address feedback with new commits → keep branch current with rebase → get approval → merge. Keep PRs small, focused, and well-described. Branch protection rules enforce quality on main.

Frequently asked questions

Is the “Pull Request Workflow on GitHub” lesson free?

Yes — the full text of “Pull Request Workflow on GitHub” is free to read here on the web, and the Frontend Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Frontend Academy course, upgrade to CoddyKit PRO.

What will I learn in “Pull Request Workflow on GitHub”?

Open a pull request on GitHub, write a helpful description, respond to code review comments, and merge when approved. You practise Frontend Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Frontend Academy?

No prior experience is required. Frontend Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Pull Request Workflow on GitHub” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Frontend Academy lesson?

Yes. Every Frontend Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Frontend Academy