> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/tips-and-tricks/workarounds/scanning-a-repository-with-different-services.md). # Scanning a repository with different services Learn how to scan a repository using different services. Debricked can handle “multiple services” in the same repository. It is common to have monorepositories with different deployments/microservices/etc. in them, but they should be logically separated in the Debricked UI. \ \ This is easy to do through the CLI. Have a look at this repository to learn how: This is how the base action looks. Debricked suggests splitting this into two separate actions to get a better overview of what service triggers what rules, and potentially only run the scans on changes in each service: {% @github-files/github-code-block url="" %} --- # 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.debricked.com/tips-and-tricks/workarounds/scanning-a-repository-with-different-services.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.