> 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/integrations/pull-request-integration/chrome-extension-pull-request-integration.md).

# Chrome Extension: Pull Request Integration

### Overview <a href="#overview" id="overview"></a>

This document explains and demonstrates where and how Chrome Extension presents **Untested Code Changes** (aka **Quality Risks** or UCCs) in an overlay over Pull Request lists and individual Pull Requests.

The Chrome Extension implemantation replaces the current PR Integration that is done with SCM (e.g. Github) API. The current implementation is limited to SCMs that provide this functionality, and is subject to how the SCM injects the data we provide into the page. The Chrome Extension implementation mitigates these limitations.

### Requirements <a href="#requirements" id="requirements"></a>

Configuration (onboarding) that includes reporting PR data can be found here: [Pull Request Integration](/knowledgebase/setup-and-configuration/integrations/pull-request-integration.md)

### Data Overlays <a href="#data-overlays" id="data-overlays"></a>

The illustrations here are from Github cloud, but this feature is supported on all popular SCM platforms (Github, Bitbucket, Gitlab, TFS, VSTS).

**Pull Request List**

Each Pull Request that Sealights has UCC data on, is annotatted with the number of UCCs in the PR. This number is an aggregate of all the UCCs in all commits included in this PR, and of all coverage types (methods/branch/lines) supported in the repository.

<figure><img src="/files/xGfzXnbP6Vkj8QfUCJ2A" alt=""><figcaption></figcaption></figure>

When the mouse is over the annotation, the annotation expands and shows the full description of the UCCs.

<figure><img src="/files/gp3Of49qCVBWdG2TeR9l" alt=""><figcaption></figcaption></figure>

**Pull Request**

When drilling down to a single Pull Request, The UCCs data is displayed in the **File changed** tab. This tab shows the full list of changed files from all commits, and reflects the changes up to and including the latest commit.

Sealighst toolbar shows the following metrics:

1. Test Stage selection drop-down
2. Coverage %
3. Number of UCCs

The metrics reflect the selected test stage, and the coverage type that can be one of the following:

1. A single coverage type (method OR branch OR line)
2. All coverage types (in case the repository includes metrics of multiple coverage types). In this case the coverage % will show value per coverage type, and the UCC count will show the sum of all UCCs of all coverage types.

<figure><img src="/files/DiqWdW9z6mA3pBjr8IVa" alt=""><figcaption></figcaption></figure>

Each code line that is identified as UCC will be annotated by a red diamond as illustrated below:

<figure><img src="/files/JxYH5YwK07Mezu1LEQCm" alt=""><figcaption></figcaption></figure>

**Toolbar Configuration**

Clicking the vertical ellipsis on the toolbar right end, will show a small popup where the user can select the following:

1. File annotations contrast: when selected the annotations in the code will appear dark
2. Coverage type: any individual type that is supported, or **All**

<figure><img src="/files/AVXM8aNi3mkceeWHhvoW" alt=""><figcaption></figcaption></figure>


---

# 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/integrations/pull-request-integration/chrome-extension-pull-request-integration.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.