> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/unifai/scanning-for-violations/scanning-in-scms/reviewing-the-pull-request.md).

# Reviewing the Pull Request

When the scan detects violations, UnifAI creates a new remediation branch and opens a pull request against the branch you scanned. The pull request contains a violations report and all code changes needed to resolve the identified issues.

The violations report in the pull request description lists the following for every fix:

| **Column**    | **Description**                                                             |
| ------------- | --------------------------------------------------------------------------- |
| Policy Name   | The UnifAI policy that the code violated.                                   |
| File          | The file where the violation was found.                                     |
| Lines Changed | The specific line numbers added, modified, or removed to fix the violation. |
| Remediation   | A description of what was changed and why.                                  |

To resolve the violations, review the changes in the pull request and merge it into your branch.

As you merge remediation pull requests and run subsequent scans, the violation count decreases. You can track this reduction across scan iterations in the violations report.

{% hint style="info" %}
The pull request is opened by the account whose PAT was used to run the scan. Ensure that token has permission to create branches and open pull requests on the repository.
{% endhint %}

### Performance and Scope

The time to complete a scan depends on the size of the repository. Use the guidance below to estimate scan duration.

| **Repository Size**   | **Guidance**                                 |
| --------------------- | -------------------------------------------- |
| Small / Medium        | Supported today. Recommended starting point. |
| Large (10,000+ files) | Coming in the next release.                  |

Up to 5 MCP server instances are supported concurrently.

#### What You Need

To scan any repository, you provide four inputs:

* Repository name
* Branch name
* SCM token (to access the repository)

### Language Model

When a remediation fix is applied, tokens are consumed to generate code from the remediation output. This averages approximately 600 tokens per violation. Token consumption is not controlled by Lineaje.

To use a different model instead of the default, configure the model in the MCP server settings. Only models that Lineaje has tested and certified are supported. Supported models include Claude Sonnet 4.5, 4.6, and Claude Opus 4.6 (SaaS supported). On-premises customers can use these models, but model configuration must be done through AWS Bedrock.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veedna.com/unifai/scanning-for-violations/scanning-in-scms/reviewing-the-pull-request.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.