> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Configuration options
**Git Integration (formerly Qodo Merge)** – AI code review agents for pull requests. This documentation describes the Qodo v1 experience. For the Qodo v2 documentation, click [here.](/code-review)
### Show possible configurations
To list all available configuration options as a PR comment, use:
```bash theme={null}
/config
```
To see which configuration settings were actually used by a specific tool (after user settings are applied), append the following flag to the tool command:
```bash theme={null}
/improve --config.output_relevant_configurations=true
```
This will output an additional field showing the actual configurations used for the `improve` tool.
### Ignoring files from analysis
To skip specific files or folders, use `ignore.glob` or `ignore.regex` patterns. You can edit these to ignore files or folders based on glob or regex patterns.
**Examples:**
Ignore all Python files in a single PR:
```bash theme={null}
/review --ignore.glob="['*.py']"
```
Ignore Python files for all PRs using glob pattern:
```bash theme={null}
[ignore]
glob = ['*.py']
```
Ignore Python files for all PRs using regex:
```bash theme={null}
[regex]
regex = ['.*\.py$']
```
### Extra instructions
All tools accept an `extra_instructions` parameter that allows you to add free-text extra instructions.
For example:
```bash theme={null}
/update_changelog --pr_update_changelog.extra_instructions="Update the version number according to these guidelines:..."
```
### Language settings
Qodo's default response language is US English. You can set the response language to a different one using the `response_language` parameter. The value should follow a locale code. See the [list of available locale codes](https://simplelocalize.io/data/locales/).
**Example:**
```bash theme={null}
[config]
response_language = "it-IT"
```
Only AI-generated text is translated. Static UI elements like labels and headers stay in English.
### Patch extra lines
By default, your PR displays three lines of unchanged code above and below each change, to provide context.
```bash theme={null}
[ code line that already existed in the file ]
[ code line that already existed in the file ]
[ code line that already existed in the file ]
- code line that was removed in the PR
+ new code line added in the PR
[ code line that already existed in the file ]
[ code line that already existed in the file ]
[ code line that already existed in the file ]
```
Qodo can increase the context around code changes, using:
```bash theme={null}
[config]
patch_extra_lines_before = 3
patch_extra_lines_after = 1
```
This helps the AI model behind Qodo Merge understand changes better. If the PR is too large, this setting may be automatically disabled.
### Log level
Control log verbosity with the `log_level` parameter.
The default log level is `DEBUG`, which provides a detailed output of all operations.
If you prefer less verbose logs, you can set higher log levels like `INFO` or `WARNING`.
```bash theme={null}
[config]
log_level = "DEBUG" # Options: DEBUG, INFO, WARNING, ERROR, CRITICAL
```
### Logging with observability tools
You can hook into logging observability tools can be used tools like LangSmith using LiteLLM callbacks:
```bash theme={null}
[litellm]
enable_callbacks = true
success_callback = ["langsmith"]
failure_callback = ["langsmith"]
service_callback = []
```
Then set these environment variables:
```bash theme={null}
LANGSMITH_API_KEY=
LANGSMITH_PROJECT=
LANGSMITH_BASE_URL=
```
### Ignoring PRs automatically
You can filter out PRs from triggering Qodo Merge using these settings:
**Ignore by Title**
You can set the `ignore_pr_title` to a list of regex patterns to match the PR title you want to ignore:
```js theme={null}
[config]
ignore_pr_title = ["\\[Bump\\]"]
```
**Ignore by Branch**
To ignore PRs from specific source or target branches, you can add the following to your `configuration.toml` file:
```js theme={null}
[config]
ignore_pr_source_branches = ['develop', 'main']
ignore_pr_target_branches = ["qa"]
```
Where the `ignore_pr_source_branches` and `ignore_pr_target_branches` are lists of regex patterns to match the source and target branches you want to ignore.
**Allow Only Specific Folders**
You can set Qodo Merge to trigger automatically only when PR changes include files in specific folders:
```js theme={null}
[config]
allow_only_specific_folders = ['folder1', 'folder2']
```
**Ignore by Label**
To ignore PRs containing specific labels, you can add the following to your `configuration.toml` file:
```bash theme={null}
[config]
ignore_pr_labels = ["do-not-merge"]
```
**Ignore by Author**
Add the following to your `configuration.toml` file to ignore PRs from specific users:
```bash theme={null}
[config]
ignore_pr_authors = ["my-special-bot-user"]
```
Where the `ignore_pr_authors` is a list of usernames that you want to ignore.
Qodo Merge also auto-detects bots using GitHub’s bot detection system. However, you can override this by explicitly listing bot usernames to ignore.
**Notice:** Bots may still receive responses if a PR they open fails tests and triggers the [`ci_feedback`](/v1/tools/tools-list/checks-ci-feedback) tool.