> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-scanning/miscellaneous/scanned-branches-in-aikido.md).
# Scanned Branches in Aikido
### Single-Branch Scanning
By default, Aikido will scan the default branch in your repository for dependency and code issues. The default branch is usually main/master. **Aikido scans your default branch on every push via SCM webhooks, plus a full re-scan of every repo, cloud, container and domain runs on a daily schedule.**
If you update the default branch, Aikido will pick up this change during its nightly sync, so no changes are needed on Aikido's end.
In some cases, it might be interesting to scan another branch instead of the default branch. This could be the case if you are developing on another branch for an extended period of time. You can overwrite the branch being scanned on the repository detail page in Aikido by clicking the branch button at the top.
A modal will appear that will allow you to change the branch that is scanned on the scheduled sync.
## Multi-Branch Scanning
If you are looking to scan multiple branches of the same repo on a regular basis, you can contact us to enable Multi-Branch Scanning for you. This is only available for Paid Plans. Please check whether multi-branch scanning is right for you [by checking the use cases in this article](/code-scanning/miscellaneous/support-for-multi-branch-scanning.md).
---
# 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://help.aikido.dev/code-scanning/miscellaneous/scanned-branches-in-aikido.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.