{"meta":{"title":"About pull requests","intro":"Use pull requests to propose, discuss, and merge changes on GitHub.","product":"Pull requests","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/pull-requests","title":"Pull requests"},{"href":"/en/enterprise-cloud@latest/pull-requests/get-started","title":"Get started"},{"href":"/en/enterprise-cloud@latest/pull-requests/get-started/about-pull-requests","title":"About pull requests"}],"documentType":"article"},"body":"# About pull requests\n\nUse pull requests to propose, discuss, and merge changes on GitHub.\n\nA pull request proposes merging code changes from one branch into another. As a collaborative feature, pull requests give you a place to discuss and review work before it becomes part of a project.\n\n## Why use pull requests\n\nPull requests turn a set of code changes into a conversation. Instead of merging work directly, you propose it so that collaborators can weigh in. This helps you and your team maintain high quality and secure code, in a few ways:\n\n* Catch bugs and problems early, before they reach the main branch.\n* Discuss and improve changes together, with feedback tied to specific lines.\n* Keep a clear, reviewable history of what changed and why.\n\n## What you can do with pull requests\n\nPull requests make your changes easy to review and validate. With a pull request, you can:\n\n* Propose changes from a branch or a fork.\n* Use stacked pull requests to break large code changes into a chain of smaller, dependent pull requests that you can review and merge independently.\n* Discuss and review the proposed changes, line by line.\n* Run automated checks, such as tests, builds, and code scanning, against the changes.\n* Respond to feedback and update the pull request as it evolves.\n* Merge the changes once reviews and required checks are satisfied.\n\n## Key parts of a pull request\n\nA pull request gathers everything you and your reviewers need into one place:\n\n* **Conversation** shows the description, comments, reviews, and a timeline of activity.\n* **Commits** shows how the branch changed over time.\n* **Checks** shows the results of automated tests, builds, and other validations.\n* **Files changed** shows the diff that reviewers comment on.\n* The **merge box** summarizes whether you can merge your changes or not. It shows what may still need to happen, such as required reviews or checks, before a pull request can be merged.\n\n## How pull requests fit your workflow\n\nWhether you're proposing changes or reviewing someone else's, a pull request follows a few stages:\n\n* **Branch or fork** the repository to create an isolated place to work.\n* **Commit** your changes as you go, building up a history of your work.\n* **Open a pull request** to propose merging your changes into the base branch.\n* **Review and discuss** the changes with collaborators, making updates as needed.\n* **Merge** the pull request when it's ready.\n\n## Next steps\n\n* [Quickstart for pull requests](/en/enterprise-cloud@latest/pull-requests/get-started/pull-request-quickstart)\n* [Quickstart for reviewing pull requests](/en/enterprise-cloud@latest/pull-requests/get-started/reviewing-pull-requests-quickstart)\n* [Writing code for a project](/en/enterprise-cloud@latest/pull-requests/concepts/writing-code-for-a-project)"}