> ## 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, Merged, or Closed                  |
| **Additions**   | Lines of code added                      |
| **Deletions**   | Lines of code removed                    |
| **CI Checks**   | Whether CI/CD checks passed before merge |
| **Merge Date**  | When the change was merged               |
| **Source**      | Integration name (e.g., GitHub, GitLab)  |

Click any code change to view the full detail page with the complete review history and CI check results.

## 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

DSALTA automatically validates these requirements by checking every merged pull request against your configured policies.

## Integrations that feed Code Changes

Connect these integrations to automatically sync code change evidence into DSALTA:

| Integration      | What syncs                                           |
| ---------------- | ---------------------------------------------------- |
| **GitHub**       | Pull requests, reviews, CI checks, branch protection |
| **GitLab**       | Merge requests, reviews, CI pipeline status          |
| **Bitbucket**    | Pull requests, reviews, branch permissions           |
| **Azure DevOps** | Pull requests, reviews, build validation             |

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

## How to read the Code Changes dashboard

The dashboard shows a summary of code change compliance across all connected repositories:

* **Total PRs** — Number of pull requests in the selected time period
* **Reviewed** — Percentage of PRs that received at least one review
* **Author ≠ Reviewer** — Percentage of PRs where the reviewer was a different person than the author
* **CI Passed** — Percentage of merged PRs where CI checks passed

If any metric falls below your configured threshold, DSALTA flags it in your compliance dashboard and generates a failing test.

## Related pages

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