The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Opening a pull request on GitHub does not merge your changes. It records a proposal to merge a head branch into a base branch, creates a shared place to review the change, and—where possible—creates temporary Git refs for the branch and a simulated merge result. From there, reviews and automated checks can happen, you can push updates to the same branch, and repository rules determine whether the change is ready to merge.
What GitHub creates when you open a pull request
A pull request (PR) proposes merging changes from one branch, called the head branch, into another, called the base branch. GitHub describes it as a proposal to merge code changes into a project. Opening the PR registers that proposal; it does not put the changes into the base branch. GitHub also creates temporary refs that integrations can use to evaluate the head branch and, when possible, a simulated merge result. GitHub Docs: About pull requests
The PR becomes a shared workspace. Its Conversation view brings together the description, comments, reviews, and activity timeline. Other views show the commits, automated check results, and changed files. The merge-status area reports whether GitHub sees blockers or requirements that still need attention.
What happens next: review, checks, and updates
Reviewers examine the change
Depending on permissions and project configuration, reviewers can comment, approve, or request changes. Reviewers can comment on the overall PR or on particular lines in the changed-files view. Anyone with read access can review and comment under GitHub’s review guidance; requesting reviews has separate permission requirements. GitHub Docs: About pull request reviews
#1 Best Overall
Automated checks run if the repository has them configured
A project may run tests, builds, security scans, or other validations through GitHub Actions or integrations. The checks you see—and whether passing them is mandatory—depend on the repository’s setup. A PR does not come with one universal checklist of tests.
You can keep working on the same pull request
To address feedback, accept a suggestion or make changes locally and push new commits to the pull-request branch. The commits and diff update on the existing PR; you do not need to open a new one just because you have added commits. Updated code may trigger checks again, depending on the repository’s configuration. Once a review conversation has been addressed, it can be marked resolved.
Draft pull requests and review requests
A draft PR signals that work is still in progress. GitHub does not allow a draft to be merged, and code owners are not automatically requested to review it. When you mark the draft ready for review, GitHub can request code-owner reviews where code-owner rules apply. GitHub Docs: Changing the stage of a pull request
Review requests also depend on access and configuration. GitHub’s guidance says an author needs write access to request reviews. A repository’s code-owner rules may automatically request review from people responsible for particular files. GitHub Docs: Requesting a pull request review
What can block a pull request from merging?
Check the PR’s merge-status area for the requirements that apply to that repository. Depending on its settings, blockers may include:
- Required approvals, including code-owner approval.
- Required status checks that have not passed.
- A branch that must be brought up to date with the base branch.
- Merge conflicts that need to be resolved.
- Other branch-protection or repository rules.
A “request changes” review is not a universal GitHub-wide veto: whether it prevents merging depends on the repository’s configured rules. Likewise, a new commit can make an approval stale if the repository has configured stale-review dismissal. Repository owners and administrators may have exception powers, so the merge panel and project contribution guidance are the best places to check the rules for a particular PR. GitHub Docs: About protected branches
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How a pull request gets merged—or closed
When the applicable requirements are satisfied, someone with the necessary permissions can merge the PR using a method enabled for that repository. The available choices are not necessarily the same from one project to another.
| Method | What it does |
|---|---|
| Merge commit | Preserves the pull-request commits and adds an explicit merge point. |
| Squash and merge | Combines the pull-request commits into one commit. |
| Rebase and merge | Places the commits onto the base branch to create linear history without a merge commit. |
| Merge queue | For eligible organization repositories using the feature, queues changes and tests them against the latest base branch before merging them in order. |
The project’s preferred history and its GitHub configuration determine which method makes sense and which choices are available. After merging, GitHub may offer the option to delete the head branch. A PR can also be closed without merging if the team decides not to take the change. GitHub Docs: About pull request merges
Recommended Free Tools
Quick Recap
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.
