---
title: "What is a pull request and what makes a good one?"  
description: "What is a pull request and what makes a good one?"  
author: "Björn Ólafsson"  
published: 2026-11-16  
updated: 2026-11-16  
canonical: https://www.mindstick.com/forum/163041/what-is-a-pull-request-and-what-makes-a-good-one  
category: "Git and DevOps"  
tags: ["pull request", "Code review", "git", "github", "teamwork"]  
reading_time: 1 minute  

---

# What is a pull request and what makes a good one?

I am a junior developer and my pull requests take days to get reviewed. How do I write a better one?

## Replies

### Reply by Daria Smirnova

A pull request (PR) is a request to merge your branch into another, usually main, and a place where teammates review the changes first.

Habits that get faster reviews:

- **Keep it small.** One purpose per PR. A 100-line change gets read carefully; a 2,000-line one gets skimmed or ignored.
- **Write a clear title and description.** Say what changed, why, and how you tested it. Link the ticket.
- **Add screenshots** for UI changes.
- **Review your own diff first.** Remove debug code and stray changes.
- **Make sure checks pass** (build, tests, lint) before asking for a review.
- **Tell reviewers where to look**, for example "the risky part is the payment retry logic".

After you get comments, reply to each one, push fixes and say when you are done. Treat feedback as feedback on the code, not on you. Also review other people's PRs; it speeds up the whole team.


---

Original Source: https://www.mindstick.com/forum/163041/what-is-a-pull-request-and-what-makes-a-good-one

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
