> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/contributing.md). # Contributing How to contribute to mirrord, the open source project, from your first issue to your first pull request. mirrord is open source and we welcome contributions! ## Getting Started * **Source code**: [github.com/metalbear-co/mirrord](https://github.com/metalbear-co/mirrord) * **Issues**: [GitHub Issues](https://github.com/metalbear-co/mirrord/issues) * **Slack**: [Join our community](https://metalbear.com/slack) ## How to Contribute 1. Fork the repository 2. Create a feature branch 3. Make your changes 4. Submit a pull request ## Greptile Reviews Greptile may review pull requests automatically. Maintainers can apply the `no-greptile` label when an automated review is not needed, such as for a typo-only or other trivial change. Opting out of reviews that are not useful helps keep usage within the included monthly review quota. If Greptile's input becomes useful later, tag `@greptileai` in the pull request to request a review explicitly. For detailed build instructions and development setup, see the [CONTRIBUTING.md](https://github.com/metalbear-co/mirrord/blob/main/CONTRIBUTING.md) in the repository. --- # 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://metalbear.com/mirrord/docs/contributing.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.