What is a pull request on GitHub and what is it for to review it?

Published on 2026-10-20 by frfrand

Qué es un pull request, cómo proponer cambios, revisar diferencias, ejecutar pruebas y hacer merge sin perder el control del proyecto.

A pull request is a proposal to integrate code changes from one branch into another, usually after discussing and reviewing them. On GitHub, it brings together the description of the change, modified files, comments, and automated checks.

It is not the same as git pull, which is a command to fetch changes. A pull request is a collaboration feature of platforms like GitHub.

Why is it needed?

Imagine an online store where three people work at the same time. One modifies the cart, another improves emails, and another adjusts payments. If they all publish directly to the main branch, it can be difficult to know what caused an error.

Branches allow working separately. The pull request provides a place to verify that a change works and is understandable before integrating it.

How it works in practice

1. You create a branch to add, for example, password recovery.
2. You modify files and save progress through commits.
3. You push that branch to the remote repository.
4. You open a pull request that proposes integrating it into the main branch.
5. You describe the problem, the solution, and how to test it.
6. Other people review the changes and can approve them or request corrections.
7. When it meets the project's requirements, the merge is performed.

If the reviewer finds a problem, you make another commit on the same branch and the pull request updates. You don't need to start another proposal from scratch every time.

What should someone review?

The first thing is to understand what problem is being attempted to solve. Then, check that the solution does not break existing functionalities.

On a payments screen, for example, it is not enough to see that the button looks good. Amounts, authorization, error handling, and possible duplicate charges must be reviewed.

Dependencies, performance, tests, security, and code clarity can also be reviewed. Small and concrete changes are usually easier to analyze than a pull request with a hundred mixed topics.

What are green checks?

GitHub allows running automatic tests, builds, and verifications through continuous integration tools. A green check indicates that those controls passed, not that the code is guaranteed against all errors.

For important projects, it is convenient to combine automatic tests with focused reviews. The appropriate depth depends on the risk of the change.

What do commenting, approving, and requesting changes mean?

A comment expresses an observation or question. An approval indicates that the reviewer considers the change acceptable. Requesting changes indicates that there are aspects that should be corrected before integrating.

According to repository rules, a minimum number of approvals or approved automatic controls may be required.

What happens when a conflict appears?

Git may not know how to combine two changes on the same lines. That does not mean the repository is broken. You need to decide what the final behavior should be, resolve the conflict, and try again.

Do not delete conflict markers at random just to make Git stop complaining. The goal is to preserve the correct logic, not to silence the message.

Does it make sense if I work alone?

Yes, in certain projects. Even without a team, opening a pull request before publishing allows you to review the scope and document why you made a change.

But not everything needs a bureaucratic process. Fixing text in a prototype may require fewer steps than modifying authentication or migrating customer data.

How to write a good description

Explain what changes, why it changes, and how it is tested. Indicate if there are migrations, new environment variables, or points that still require attention. Attach screenshots if the interface changed.

"Various fixes" does not help whoever reviews today nor whoever tries to understand the history in six months.

Where does ArduMaker fit in?

Projects deployed from Git on ArduMaker VPS can benefit from a prior review on GitHub: this way the team checks the changes before activating a new deployment. The pull request is part of the repository process, not an automatic quality guarantee.

In summary: a pull request turns a modification into a verifiable, discussable, and reversible proposal within the team's workflow.

Sources: Pull requests according to GitHub · Review guide · Branches and merge explained.