A pull request (PR) proposes merging changes from one branch into another; it is not the merge itself. On GitHub, it also gives contributors a shared place to discuss the changes, review them, and check that repository requirements are met before integration.
How a pull request works
A typical workflow is: create a branch or fork, make and commit changes, open a pull request, respond to review and update the branch, then merge when the repository’s requirements are satisfied. The source branch containing your work is the head; the destination branch is the base. Choosing the wrong base or compare branch can propose the wrong changes, so check both before opening the PR.
As an Amazon Associate I earn from qualifying purchases.
A focused change with a clear title and description is easier to understand. GitHub Docs notes that smaller pull requests are faster to review and easier to merge, though it does not prescribe a universal ideal size. See GitHub’s explanation of pull requests.
How do I create a pull request?
GitHub’s quickstart describes creating a PR through the website or GitHub CLI. Use a branch in the repository if you have permission to write to it; otherwise, fork the repository and work from your fork. Exact interface labels and permissions may vary with repository settings.
#1 Best Overall
Before opening it
- Make a focused change and commit it with a message that describes the work.
- If working locally, push the branch so GitHub can compare it.
- Check that the branch you changed contains the commits you intend to propose.
On the GitHub website
- Open the repository and select Pull requests, then New pull request.
- Choose the base branch that should receive the work and the compare branch that contains your changes. Inspect the proposed diff.
- Enter a concise title and a description that explains what changed and why. Include relevant context or testing information that will help reviewers assess it.
- Create the PR as ready for review if you want feedback now, or choose draft if the work is not ready.
- Request an appropriate reviewer if you have the required access. GitHub says requesting a review requires write access; people or teams with read access can be requested. Multiple-reviewer and team options can depend on repository visibility and plan.
With GitHub CLI
After committing and pushing your branch, run gh pr create from the repository. The CLI guides you through creating the PR; check the selected base and head, title, and description before submitting. Consult the GitHub pull request quickstart for the documented website and CLI routes and current workflow details.
Direct branch or fork?
| Approach | Use it when |
|---|---|
| Branch in the repository | You have permission to write to that repository. |
| Fork | You do not have write access; make your branch in your fork and propose its changes to the original repository. |
What is a draft pull request?
A draft PR shares work in progress without presenting it as ready for formal review. Choose draft when you want early visibility or discussion but still expect substantial work. A draft cannot be merged, and code owners are not automatically requested while it remains a draft. Mark it ready for review when you want formal review; that action requests review from code owners. See GitHub’s guidance on changing a PR’s stage.
Rank #2
| Status | What it signals | Important effect |
|---|---|---|
| Draft | Work is not ready for formal review. | Cannot be merged; code owners are not automatically requested until it is marked ready. |
| Ready for review | The author is asking for review. | Review can be requested, including from code owners under the documented workflow. |
How do I review a pull request?
- Understand the goal. Read the PR title, description, and relevant discussion before judging individual lines.
- Inspect the change. Review the files and diff; look at commits and status checks when they help explain the change or its validation.
- Leave actionable feedback. Comment on the specific issue, preferably near the relevant line. If you know the exact edit, use a suggested change. GitHub’s review interface allows pending comments to be submitted together.
- Submit a review decision. Choose Comment, Approve, or Request changes, and explain concerns clearly enough that the author can act on them.
GitHub describes the meanings of these review states in its pull request review documentation. An approval communicates readiness, but it does not by itself guarantee that a PR can merge.
Free tools Windows power users keep installed
One-click scans. No signup required.
Comment, Approve, or Request changes?
| Decision | Meaning |
|---|---|
| Comment | Give feedback without recording an approval or a request for changes. |
| Approve | Signal that you consider the changes ready from your review. |
| Request changes | Flag work you believe should be addressed before proceeding. |
A request for changes does not universally block merging. Whether it does depends on repository branch protection or ruleset requirements and the reviewer’s permissions.
How to respond to review feedback
As the author, read each comment for the issue it is raising, not just the suggested wording. Apply a suggestion when it fits; otherwise, explain your reasoning in the conversation. For broader changes, make and commit an update to the PR’s branch. The existing PR updates as commits are added to that branch.
- Resolve a conversation once its concern has been addressed or discussed to an agreed outcome.
- After substantial updates, request another review as appropriate.
- Before merge, check for outstanding reviews and required status checks rather than assuming that a new commit or approval cleared every requirement.
GitHub’s documentation covers responding to reviewer comments.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do I merge a pull request?
First inspect the PR’s status area and any repository-specific contribution guidance. Required approvals and checks must be satisfied in the quickstart workflow before merging, but the exact requirements are configured per repository. They can differ, so do not assume that one approval—or any particular review outcome—will always be enough.
Recommended Free Tools
- Confirm the PR targets the intended base branch and that its changes are ready.
- Review the status area for required approvals, checks, and other indicated blockers.
- Address unresolved feedback or failing requirements, then re-check the status.
- When GitHub makes the merge action available and repository guidance permits it, merge using the repository’s configured workflow.
For the documented process, see the GitHub quickstart and the repository’s own rules. Draft PRs cannot be merged.
Common problems and what to check
- The PR shows the wrong changes: Check the base and compare branches, then inspect the diff before asking for review.
- You cannot open a PR directly against the repository: You may lack write access. Fork it, push your work to the fork, and propose those changes to the original repository.
- You cannot request a review: Review requests require write access according to GitHub’s quickstart. Ask a repository maintainer about the appropriate route if you lack it.
- The draft cannot be merged: That is expected. Mark it ready for review when it is ready to proceed.
- The merge action is unavailable despite an approval: Check the PR status area for required approvals, checks, or other repository-configured rules. An approval alone is not a universal merge guarantee.
- A request for changes appears not to block merging: Blocking behavior depends on branch protection or ruleset configuration and reviewer permissions; inspect the repository’s requirements rather than assuming a universal rule.
Or skip the browser setup
If your workflow needs a clean screenshot of a page—for documentation, an issue, or a review artifact—you can call ScreenshotNeo, a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF. See the ScreenshotNeo documentation for request options.
Quick Recap
cURL example:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://github.com -o shot.webpScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up free for 1,000 screenshots a month, with no card required.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
