Learn about pull requests and draft pull requests on GitHub. Pull requests communicate changes to a branch in a repository. Once a pull request is opened, you can review changes with collaborators and add follow-up commits.
A pull request (often referred to as “PR”) is a proposal to merge a set of changes from one branch into another. By creating a pull request, you can review a set of changes with others before they are incorporated into the main code base.
PullRequests are a feature of online git services like Github and Gitlab. They allow anyone to request for changes to be added, even if they don't have access to the repository.
In this article, we’ll explore everything you need to know about pullrequests in Git—what they are, how they work, and how to create, review, and merge pullrequests effectively.
When you file a pullrequest, all you’re doing is requesting that another developer (e.g., the project maintainer) pulls a branch from your repository into their repository.
What Is a Pull Request? A pull request is really a method to suggest changes to code. So imagine you're working on a feature or in a separate branch, a pull request lets you ask to merge those changes into the main codebase. This is usually done after others have had a chance to review them.
Think of a pullrequest as the difference between sliding a handwritten note under someone's door and having a focused meeting about a specific topic. The note might convey information, but the meeting creates opportunity for dialogue, clarification, and collaborative refinement.
PullRequest explained with real examples: Learn what a pullrequest is, how to create one, where it fits in development, and why pullrequests are vital for code review in 2025.
A pullrequest (often shortened to PR) is your way of asking the project maintainers to pull your changes from your branch and merge them into the main, or master, branch.
A pull request is a formal way to propose changes to a repository you don’t own, allowing the project maintainers to review, discuss, and merge your work. Whether you’re fixing a bug, adding a feature, or improving documentation, knowing how to craft a clear, well-structured PR is essential for successful collaboration.
