> 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/r/repository.md). # Repository A central place where data is stored and managed. A repository (often shortened to "repo") is a central storage location for managing and tracking changes to files, typically source code. In version control systems like Git, a repository contains the complete history of all changes, branches, and tags, along with metadata about each commit. Repositories can be local (on a developer's machine) or remote (hosted on platforms like GitHub, GitLab, or Bitbucket). Remote repositories enable collaboration by providing a shared location where team members push and pull changes. Repositories can be public (visible to everyone) or private (restricted to authorized users). In API and serverless development, repositories typically contain application code, API specifications (such as OpenAPI documents), API gateway configuration files, infrastructure-as-code definitions, and CI/CD pipeline configurations. A well-organized repository structure makes it easier for teams to manage API versioning, review configuration changes through pull requests, and automate deployments through CI/CD pipelines triggered by commits to specific branches. --- # 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/r/repository.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.