A pull request is a request to merge a set of code changes into a shared branch, where teammates can review them first. The author opens it from a branch, describes the change and invites comments, and automated checks such as tests usually run against it. Once reviewers approve and the checks pass, the change is merged. Some platforms call the same thing a merge request.
Pull requests give teams a record of what changed and why, and they are a point where defects, design problems and security issues can be caught before they reach the main branch.
Their value depends on how they are used. Very large pull requests are hard to review carefully and often receive shallow feedback, and long waits for review slow work down. An approval shows that someone looked at the change, not that it is correct, and automated checks only test what they were written to test.
To keep them effective, make changes small and focused, write a clear description, set expectations for how quickly reviews happen and make sure the required checks cover the risks that matter. Track how long pull requests wait so that delays are visible.