> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Code Changes

> Read-only evidence feed from code repositories — proves code review compliance for auditors.

The Code Changes page provides a read-only evidence feed from your connected code repositories. It shows pull requests, code reviews, and merge activity — proving to auditors that your team follows proper code review practices.

This module is **integration-only**. DSALTA pulls data directly from your code repositories using read-only API access. Manual entries are not supported because the value of this module is that evidence comes directly from the source system.

## What DSALTA pulls

For each pull request or merge request, DSALTA captures:

| Column          | Description                                                                   |
| --------------- | ----------------------------------------------------------------------------- |
| **PR Number**   | Pull request or merge request number                                          |
| **Title**       | Title of the code change                                                      |
| **Repository**  | Which repository the change was made in                                       |
| **Author**      | Who wrote the code                                                            |
| **Reviewer(s)** | Who reviewed and approved the code                                            |
| **Status**      | **Open** or **Merged**. A pull request closed without merging stays **Open**. |
| **Additions**   | Lines of code added                                                           |
| **Deletions**   | Lines of code removed                                                         |
| **Merge Date**  | The merge timestamp, read from GitHub and shown in the row's detail panel     |
| **Source**      | Integration name (e.g., GitHub, GitLab)                                       |

Click any code change to open its detail panel, which shows the same fields alongside the change description.

## Why this matters for compliance

Auditors reviewing SOC 2 (CC8.1) and ISO 27001 (A.14.2.1) need evidence that:

* Code changes are reviewed by at least one person who is **not the author** (author ≠ reviewer)
* Changes pass automated checks (CI/CD) before being deployed
* No changes are force-pushed or merged without review
* Branch protection rules are enforced on production branches

This page is the evidence feed an auditor reads to see that. The automated change-management checks — *Change request approved before implementation*, *Peer review enforced for code changes*, *Code changes reviewed before merging* — evaluate the records on your [Changes](/guides/assets/changes) page, so keep that page populated as well.

## Integrations that feed Code Changes

Four integrations sync code change evidence into DSALTA:

| Integration      | What syncs                                                       |
| ---------------- | ---------------------------------------------------------------- |
| **GitHub**       | Pull requests with author, reviewers, line counts and merge date |
| **GitLab**       | Merge requests with author, line counts and merge date           |
| **Bitbucket**    | Pull requests with author, reviewers, line counts and merge date |
| **Azure DevOps** | Pull requests with author, reviewers, line counts and merge date |

To connect an integration, go to **Integrations** in the DSALTA sidebar.

## How to read the Code Changes dashboard

Three cards sit above the table, each a count of the pull requests currently loaded:

* **Total PRs** — every pull request on the page
* **Merged** — those with status Merged
* **Open** — those with status Open

Use the table itself for review evidence: sort or filter by **Reviewer(s)** to find changes merged without a named reviewer, and compare it against **Author** to demonstrate that someone other than the author approved the change.

## Related pages

* [Changes](/guides/assets/changes)
* [Integrations](/integrations/overview)
* [GitHub Integration](/integrations/github)
* [GitLab Integration](/integrations/gitlab)

## GitHub reconnect banner

<AccordionGroup>
  <Accordion title="A banner says to disconnect and reconnect GitHub" icon="triangle-exclamation">
    If you see an amber **Action Required** banner asking you to disconnect and reconnect your GitHub account, your GitHub connection was made before DSALTA needed the additional read permissions this page depends on. The **Go to Integrations** button takes you to the right place.

    Reconnecting means disconnecting first, which permanently deletes the data and tests already collected from GitHub — read [Integration errors](/troubleshooting/integration-errors) before you start.

    The banner clears itself after about a week per browser, whether or not you acted on it. Its disappearance is not confirmation that the reconnect happened.
  </Accordion>
</AccordionGroup>