> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/p/pull-request.md). # Pull Request A method of submitting contributions to a development project. It is a request for the project maintainer to pull a branch from a repository, review it, and merge it into the main codebase. A pull request (PR) is a mechanism in version control platforms like GitHub, GitLab, and Bitbucket for proposing changes to a codebase. A developer creates a branch, makes changes, and opens a pull request to ask the project maintainers to review and merge the changes into the main branch. Pull requests provide a structured workflow for code review, discussion, and quality assurance. They typically display a diff of all changes, allow inline comments, and can trigger automated checks such as CI/CD pipelines, linting, and test suites. Approval requirements can be configured to ensure that changes are reviewed by the appropriate team members before merging. In API and infrastructure projects, pull requests are used to review not only application code but also API gateway configurations, routing rules, and deployment scripts. Changes to rate limiting policies, authentication settings, or API specifications can be reviewed in a pull request, providing an audit trail and reducing the risk of misconfigurations reaching production. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/p/pull-request.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.