---
title: 'Map GitHub Context'
metadesc: 'Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.'
canonical: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/'
page_id: 'qi-home-map-github-context'
---

# Map GitHub Context


**Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.**

For GitHub App setup on the developer side, see [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/).

---

When your developers open or update pull requests in GitHub, Atto detects them and shows them in the **Unmapped Context** view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks.

Once mapped, Atto generates new test cases or updates existing ones based on the code changes in that pull request.

---

> ## **Prerequisites**
>
> Before you begin, ensure that:
> - Your GitHub account is connected to your project. Go to **Settings > Integrations** to connect.
> - At least one sprint or Ad-Hoc session exists with generated test cases.

---

## **View Unmapped GitHub Context**

1. From the left navigation, go to **QI Home**.

2. In the left sidebar, click **View** next to **Unmapped Context**.

3. The **Unmapped Context** tab opens. GitHub PRs are identified by the GitHub PR badge.

Each GitHub PR entry shows:

- **PR title**: The pull request title.
- **Repository**: The repository and branch the PR is from.
- **Author**: The developer who opened the PR.
- **Lines changed**: Lines added and removed.
- **Time**: When the PR was opened or last updated.
- **AI Suggestion**: The module Atto recommends mapping this PR to.

---

## **Map a GitHub PR to a Sprint**

1. On the PR you want to map, click **Map to Module**.

2. In the **Map to Module** dialog, select the **Project** from the dropdown.

3. Under **Map to**, select **Sprint**.

4. Select the **Sprint** you want to map this PR to.

5. Select the **Stories** within the sprint that this PR relates to.

6. Review the **What happens next** message: "This PR will be mapped to the selected stories in the sprint and test cases will be auto-generated by Atto."

7. Click **Map**.

Atto triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes.

---

## **Map a GitHub PR to an Ad-Hoc Session**

1. On the PR you want to map, click **Map to Module**.

2. In the **Map to Module** dialog, select the **Project**.

3. Under **Map to**, select **Adhoc**.

4. Under **Existing Adhoc Session**, select the session you want to map to, or select **+ Create New Adhoc Session** to start a new one.

5. Click **Map**.

---

## **Map Multiple PRs at Once**

1. Select the checkboxes next to the PRs you want to map.

2. A bottom action bar appears showing the number of PRs selected and a **Map to Module** button.

3. Click **Map to Module**.

4. In the **Map to Module** dialog, the selected PRs are listed at the top. Configure the mapping settings and click **Map**.

---

## **Dismiss a GitHub PR**

If a PR is not relevant to your test coverage, click **Dismiss**. The PR is removed from the Unmapped Context list.

> **NOTE**:
> Dismissed context does not contribute to coverage. You cannot recover dismissed context from this view.

---

## **View Mapped Context**

1. In the Unmapped Context view, click the **Mapped Context** tab.

The Mapped Context tab shows:

- **Total Mapped**: The number of context entries successfully mapped.
- **Tests Generated**: The number of test cases generated from mapped context.
- **Sprints Covered**: The number of sprints that received test updates from mapped context.

Each mapped context entry shows the sprint and story it was mapped to, and the number of test cases generated.

---