Suggest an editImprove this articleRefine the answer for “What does "pull request" mean?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)A **Pull Request (PR)** is a request to merge changes from one branch into another (usually from a feature branch into `main` or `develop`). **Key point:** it is the main tool for code review and collective quality control in Git projects.Shown above the full answer for quick recall.Answer (EN)ImageA **Pull Request (PR)** is a request to merge changes from one branch into another (usually from a feature branch into `main` or `develop`). It is the main tool for **code review and collective quality control** in Git projects. --- ### How it works 1. A developer creates a new branch, makes commits, and pushes it to the repository. 2. Once the work is done, they open a **pull request** in the system (GitHub, GitLab, Bitbucket). 3. In the PR, they provide: - a description of the changes, - related tasks or tickets, - possible risks. 4. Colleagues (reviewers) check the code, leave comments, and suggest fixes. 5. After the fixes and approval, the PR is merged into the target branch. --- ### Why it is needed - for **code review** before code is merged; - for **transparency of changes** - it is visible who made a change and why; - for **automatic checks** (CI runs tests on every PR); - for **documenting the development history**. --- ### Example A developer opens a PR: > "Added an API for user registration (#123)" > Colleagues review it, the tests pass, the PR is approved and merged into `develop`. --- ### Conclusion A **pull request** is a "checkpoint" between writing code and integrating it. It combines review, testing, and discussion, ensuring a **high-quality and safe merge of changes**.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.