# Pull requests documentation Discover how to create, review, and merge pull requests, resolve merge conflicts, and work with forks. ## Recommended * [About pull requests](/en/enterprise-server@3.22/pull-requests/get-started/about-pull-requests) Use pull requests to propose, discuss, and merge changes on GitHub. * [Branches](/en/enterprise-server@3.22/pull-requests/reference/branches) Use branches in GitHub to isolate development work, manage default branches, and collaborate effectively using pull requests and branch protections. * [Creating a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/creating-a-pull-request) Create a pull request to propose changes to the code in a repository. * [Reviewing proposed changes in a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/reviewing-proposed-changes-in-a-pull-request) Review commits, file changes, and diffs in pull requests to provide feedback, approve changes, or request updates before merging. * [Merging a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/merging-a-pull-request) Merge pull requests into the upstream branch, choose merge methods, and meet repository requirements like reviews or status checks. * [Resolving a merge conflict on GitHub](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/resolving-a-merge-conflict-on-github) Resolve simple merge conflicts directly on GitHub using the conflict editor or handle complex cases via the command line. * [Fork a repository](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/fork-a-repo) Fork a repository on GitHub to propose changes, collaborate on projects, and manage your own copy of the codebase. * [Commits](/en/enterprise-server@3.22/pull-requests/reference/commits) Learn how commits save changes to your files, track authorship, and organize your project's history in GitHub. ## Links ### Getting started * [About pull requests](/en/enterprise-server@3.22/pull-requests/get-started/about-pull-requests) Use pull requests to propose, discuss, and merge changes on GitHub. ## Articles * [About pull requests](/en/enterprise-server@3.22/pull-requests/get-started/about-pull-requests) Use pull requests to propose, discuss, and merge changes on GitHub. * [About forks](/en/enterprise-server@3.22/pull-requests/get-started/about-forks) Use forks to make changes in your own copy of a repository and propose them back to the original project. * [Quickstart for pull requests](/en/enterprise-server@3.22/pull-requests/get-started/pull-request-quickstart) Propose your first change and take it all the way from your first commit to a merged pull request. * [Quickstart for reviewing pull requests](/en/enterprise-server@3.22/pull-requests/get-started/reviewing-pull-requests-quickstart) Review a pull request by leaving comments, making suggestions, and approving or requesting changes. * [Writing code for a project](/en/enterprise-server@3.22/pull-requests/concepts/writing-code-for-a-project) Use branches, forks, commits, and pull requests to safely write, refine, and propose code changes for collaborative projects. * [Helping others review your changes](/en/enterprise-server@3.22/pull-requests/concepts/helping-others-review-your-changes) Create clear, focused pull requests that improve collaboration, streamline reviews, and keep your team informed about your changes. * [Giving reviews](/en/enterprise-server@3.22/pull-requests/concepts/giving-reviews) Provide feedback on pull requests by commenting on changes, suggesting edits, and approving or requesting updates before merging code. * [Resolving reviews](/en/enterprise-server@3.22/pull-requests/concepts/resolving-reviews) Address review feedback by comparing changes, updating code, and resolving comments to prepare your pull request for merging. * [Deploying code](/en/enterprise-server@3.22/pull-requests/concepts/deploying-code) Validate pre-deployment checks, choose merge strategies, and manage branches effectively when deploying code. * [Managing branches within your repository](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/managing-branches-within-your-repository) Create new branches for development and delete unused branches directly on GitHub. * [Committing changes to a pull request branch created from a fork](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/committing-changes-to-a-pull-request-branch-created-from-a-fork) Commit changes to a pull request branch created from a fork by obtaining the necessary permissions and using Git commands effectively. * [Creating a commit with multiple authors or on behalf of an organization](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/creating-a-commit-with-multiple-authors) Attribute commits to multiple authors or organizations using trailers in commit messages for better collaboration and transparency. * [Changing a commit message](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/changing-a-commit-message) Amend unclear, incorrect, or sensitive commit messages locally and push updated commits to GitHub, including steps for editing recent or older commits. * [Comparing commits](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/comparing-commits) Compare branches, tags, commits, forks, and dates to analyze changes and track repository history effectively. * [Troubleshooting commits](/en/enterprise-server@3.22/pull-requests/how-tos/commit-changes/troubleshooting-commits) Resolve common commit issues like incorrect user links, missing local commits, and push protection blocks. * [Creating a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/creating-a-pull-request) Create a pull request to propose changes to the code in a repository. * [Creating a pull request from a fork](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/creating-a-pull-request-from-a-fork) Create a pull request from a fork to propose changes to an upstream repository and collaborate on code effectively. * [Changing the stage of a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/changing-the-stage-of-a-pull-request) Mark a draft pull request as ready for review or convert an open pull request back to a draft to manage your workflow effectively. * [Keeping your pull request in sync with the base branch](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch) Update your pull request branch with changes from the base branch to resolve conflicts and ensure compatibility before merging. * [Changing the base branch of a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/changing-the-base-branch-of-a-pull-request) Modify the base branch of an open pull request to compare changes against a different branch and ensure accurate updates. * [Requesting a pull request review](/en/enterprise-server@3.22/pull-requests/how-tos/create-pull-requests/requesting-a-pull-request-review) Request reviews for your pull requests from individuals or teams to ensure thorough feedback and collaboration. * [Stacked pull requests](/en/enterprise-server@3.22/pull-requests/how-tos/stacked-pull-requests) Use stacked pull requests to break large code changes into a chain of smaller, dependent pull requests you can review and merge independently. * [Checking out pull requests locally](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/checking-out-pull-requests-locally) Check out pull requests locally to resolve merge conflicts, test changes, or modify code. * [Reviewing proposed changes in a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/reviewing-proposed-changes-in-a-pull-request) Review commits, file changes, and diffs in pull requests to provide feedback, approve changes, or request updates before merging. * [Reviewing dependency changes in a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/reviewing-dependency-changes-in-a-pull-request) Review dependency changes in pull requests to identify added, updated, or removed dependencies and detect vulnerabilities before they reach production. * [Commenting on a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/commenting-on-a-pull-request) Leave comments on pull requests in GitHub, including general feedback, line-specific suggestions, and file-level discussions to enhance collaboration and code reviews. * [Approving a pull request with required reviews](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/approving-a-pull-request-with-required-reviews) Approve pull requests with required reviews, including setting approval rules, reviewing changes, and submitting feedback before merging. * [Viewing a pull request review](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/viewing-a-pull-request-review) View and navigate all comments from a single pull request review to understand changes and feedback. * [Dismissing a pull request review](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/dismissing-a-pull-request-review) Dismiss outdated or unapproved pull request reviews and update their status with a required comment. * [Incorporating feedback in your pull request](/en/enterprise-server@3.22/pull-requests/how-tos/review-pull-requests/incorporating-feedback-in-your-pull-request) Apply suggested changes directly to a pull request, batch multiple suggestions into a single commit, or open an issue to track out-of-scope feedback. * [Resolving a merge conflict on GitHub](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/resolving-a-merge-conflict-on-github) Resolve simple merge conflicts directly on GitHub using the conflict editor or handle complex cases via the command line. * [Resolving a merge conflict using the command line](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/resolving-a-merge-conflict-using-the-command-line) Resolve merge conflicts using the command line by identifying conflicting changes, editing files, and committing resolutions. * [Troubleshooting required status checks](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks) Resolve common errors and unblock merging or pushing to protected branches by troubleshooting required status checks. * [Merging a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/merging-a-pull-request) Merge pull requests into the upstream branch, choose merge methods, and meet repository requirements like reviews or status checks. * [Merging a pull request with a merge queue](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/merging-a-pull-request-with-a-merge-queue) Use merge queues in GitHub to streamline pull request merging, ensure required checks pass, and manage queue operations effectively. * [Automatically merging a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/automatically-merging-a-pull-request) Enable or disable auto-merge for pull requests to streamline your workflow and automatically merge changes once all requirements are met. * [Reverting a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/reverting-a-pull-request) Create a new pull request to revert a previously merged pull request and address merge conflicts if they arise. * [Closing a pull request](/en/enterprise-server@3.22/pull-requests/how-tos/merge-and-close-pull-requests/closing-a-pull-request) Close a pull request without merging it to manage unnecessary changes or address alternative solutions in other branches. * [Fork a repository](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/fork-a-repo) Fork a repository on GitHub to propose changes, collaborate on projects, and manage your own copy of the codebase. * [Configuring a remote repository for a fork](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/configuring-a-remote-repository-for-a-fork) Set up a remote pointing to the upstream repository in Git to sync changes between your fork and the original repository. * [Syncing a fork](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/syncing-a-fork) Sync a forked repository with its upstream repository using the web interface, GitHub CLI, or command line. * [Allowing changes to a pull request branch created from a fork](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) Enable collaboration by allowing repository maintainers to commit changes to pull request branches created from forks in your personal account. * [Detaching a fork](/en/enterprise-server@3.22/pull-requests/how-tos/work-with-forks/detaching-a-fork) Disconnect a repository from its fork network by leaving the network or creating a standalone repository through manual steps. * [Pull requests](/en/enterprise-server@3.22/pull-requests/reference/pull-requests) Propose, review, and merge code changes using pull requests to collaborate effectively and maintain code quality. * [Branches](/en/enterprise-server@3.22/pull-requests/reference/branches) Use branches in GitHub to isolate development work, manage default branches, and collaborate effectively using pull requests and branch protections. * [Forks](/en/enterprise-server@3.22/pull-requests/reference/forks) Understand how forks enable independent collaboration by creating separate repositories connected to the original, with distinct settings and permissions. * [Commits](/en/enterprise-server@3.22/pull-requests/reference/commits) Learn how commits save changes to your files, track authorship, and organize your project's history in GitHub. * [Using query parameters to create a pull request](/en/enterprise-server@3.22/pull-requests/reference/using-query-parameters-to-create-a-pull-request) Use query parameters to create custom URLs that open pull requests with pre-filled titles, descriptions, labels, and more. * [Pull request reviews](/en/enterprise-server@3.22/pull-requests/reference/pull-request-reviews) Review pull requests to provide feedback, suggest changes, and ensure code quality before merging. * [Status checks](/en/enterprise-server@3.22/pull-requests/reference/status-checks) Understand how status checks ensure commits meet repository conditions, assist pull request reviews, and manage validations like builds, tests, and deployments. * [Pull request merges](/en/enterprise-server@3.22/pull-requests/reference/pull-request-merges) Learn strategies for merging pull requests, including merge commits, squash merges, and rebases, to manage repository history effectively. * [Merge conflicts](/en/enterprise-server@3.22/pull-requests/reference/merge-conflicts) Identify and resolve merge conflicts in Git to ensure smooth branch integration and successful pull request merges. * [Managing and standardizing pull requests](/en/enterprise-server@3.22/pull-requests/reference/managing-and-standardizing-pull-requests) Manage and standardize pull requests using templates, code owners, protected branches, rulesets, and automated tools for consistent and secure repository contributions. * [Working with pre-receive hooks](/en/enterprise-server@3.22/pull-requests/reference/working-with-pre-receive-hooks) Enforce repository policies and prevent issues like secrets or invalid commits using pre-receive hooks on GitHub Enterprise Server.