> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/chrome-extension-pull-request/quality-risks-exceed-code-changes.md).

# Quality Risks Exceed Code Changes

## Problem <a href="#problem" id="problem"></a>

I see a higher number of QRs in the Chrome Extension than the amount of modified/added code of my Pull Request. Few of the QRs are even in files not modified in my specific PR !

## Cause #1 (Most common) <a href="#cause-1-most-common" id="cause-1-most-common"></a>

The target branch contains commits that were not merged from the target branch to the pull request branch

<figure><img src="/files/tQ64R0sm35A29z7t9giT" alt="" width="563"><figcaption></figcaption></figure>

## Solution #1 <a href="#solution-1" id="solution-1"></a>

Configure the pull request flow to merge from the target branch (even if done locally) prior to running the build scanner

{% code overflow="wrap" lineNumbers="true" %}

```
//retrieve the PR source code from the Git based SCM
git clone git@github.repo/repo.git
​
//create a local integration branch starting from the target branch - do not push it to the remote
git checkout -b <local-integration-branch-name> <target-branch>
​
//Merge pull request into local integration branch
git pull --ff git@github.repo/repo.git <pull-request-branch>
​
...
//run sealights build
```

{% endcode %}

## Cause #2 <a href="#cause-2" id="cause-2"></a>

The target branch contains commits that were not reported to SeaLights and the user merged from the target branch to the pull request branch.

{% hint style="warning" %}
A common reason is with target branch that have builds reported based on predefined frequency (hourly, daily) rather than after every single merge (commit) to that branch.\
Sealights recommendation is for the later option.
{% endhint %}

<figure><img src="/files/XIwrMRVW3D90RsDD3jVS" alt="" width="563"><figcaption></figcaption></figure>

## Solution #2 <a href="#solution-2" id="solution-2"></a>

Validate in the CI server (Jenkins, Bamboo…) that the every commit from the SCM (target branch) is reported to Sealights via an automated build.\
If not, initiate a build from both the target branch and then the PR branch.


---

# 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.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/chrome-extension-pull-request/quality-risks-exceed-code-changes.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.