A proposal, not a command
A pull request (PR) is like handing a draft to an editor: “I think this is ready. Would you take a look?” A developer shares a branch in an online repository, then opens a PR through a Git hosting provider. GitLab calls it a merge request. Its page shows lines added, changed, or removed; any automated check results; and the team’s discussion.
During code review, reviewers may ask questions, suggest changes, or approve the work. When the team is satisfied and required checks pass, the branch can be merged into its target, often called main. Merging updates the shared code, but users may not see the change until it is deployed and released.
What PMs and designers should look for
A PR can show what was built. A clear one links to the ticket or design, explains trade-offs, and says how to test the change. Screenshots or videos let product and design colleagues check behaviour and wording without reading code. After merging, CI/CD can help move the change toward users.