Skip to main content
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: 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 page, so keep that page populated as well.

​
Integrations that feed Code Changes

Four integrations sync code change evidence into DSALTA: 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.

​
GitHub reconnect banner

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