Skip to main content
Video tutorial · 0:54

Compliance report

The compliance report is the evidence file for an audit: for a period, every merge request handled under change management with its policy, decision, approval, scans and merge, the changes that reached a branch under change management without a merge request, the company's audit trail and a summary of background jobs. It is downloaded as a CSV or a PDF file.

Who may export it​

Platform admins, company admins and auditors (the roles that read the audit log). Policy managers and users cannot. A platform admin exports the report of the company selected in the header.

Exporting it​

Audit log → Export report, then Download. The panel and its settings (From, To, Changes, Format) are described in Audit log → Export report.

  • Period: whole days in the company's time zone (company General tab; UTC when it is not set), the end day included. By default the last 30 days.
  • Changes: Merged in the period (the default) covers the merge requests merged between the two dates; Opened in the period those opened between them (on the VCS; when the VCS did not say, when Merge Pilot first recorded them).
  • Format: CSV or PDF.

The download is named compliance-report-<company>-<from>-to-<to>.csv (or .pdf). When a part was cut at its limit, the page says Report truncated and names each part cut, for example Audit entries: 5,000 of 6,120 included. Use a shorter date range for complete data. (the parts are Merge requests, Audit entries and Changes outside change management); otherwise Report downloaded successfully.

What is in it​

Merge requests​

The merge requests of the company in the period, oldest first, that were under change management:

  • merge requests of watched repositories are left out (the monitoring report covers them), except one that merged without approval while under change management;
  • merge requests imported from a watched repository's history are left out.

Changes outside change management​

Direct changes found in the period on branches of repositories under change management, oldest first. Changes to watched repositories are not in it. Nothing is listed when the company does not record direct changes.

Audit trail​

The company's audit log entries of the period, oldest first: time, user name, action, resource, resource ID, result and IP address. Platform entries (those of no company) are not in it. The actions are listed in Audit log → Audit actions.

Job processing summary​

The company's background jobs created in the period, per job type: total, completed and failed. See Jobs.

Limits​

FormatMerge requestsChanges outside change managementAudit entries
CSV10,00010,00010,000
PDF2,0002,0005,000

The first entries of the period, oldest first, are kept. A part that was cut says so in the file.

The CSV file​

The file starts with a byte-order mark so spreadsheets read it as UTF-8. A value that starts with =, +, -, @, a tab or a carriage return (a title, an author, a branch name, a commit title, anything the report's data fills in) is prefixed with ' so spreadsheets do not read it as a formula. Times are in the company's time zone, with the zone's name (2026-10-26 14:05:00 CET). Yes/no columns are true or false. It holds, one after the other, separated by an empty row:

Header: === Compliance Evidence Report ===, then Company, Period, Period applies to (merge date or opening date), Generated, Generated By, and a Note for each part that was cut (MR data truncated: N of M records included).

=== Merge Request Evidence (N records) ===, one row per merge request:

ColumnShows
RepoThe repository's ID on the VCS
MR#, Title, AuthorAs on the VCS
Source Branch, Target BranchIts branches
Stateopened, merged, closed or out_of_scope
OpenedWhen it was opened on the VCS (when the VCS did not say, when Merge Pilot first recorded it)
Merged At, Merged ByWhen and by whom it merged
Merged CommitThe merge request's head commit when it merged
Approved CommitThe head commit the approved change approval covered (empty unless the change approval is approved)
Merged Commit Approvedtrue when the merged commit is the approved one
Separation Of DutiesThe separation-of-duties exceptions noted on the merge request, separated by ;
SoD Violationtrue when a policy that forbids it saw an approver merge the merge request
Merged In FreezeThe name of the change freeze it merged in, against it
Approval Revoked After Mergetrue when the change approval's approval was withdrawn in the tracker after the merge
Policy, Policy VersionThe policy that covered it and the version
Change Typestandard, normal or emergency
PriorityThe policy's priority
GateThe merge gate: approved, pending or blocked
Gate CommitThe head commit the decision was made for
Open ControlsEach enforced control that did not pass, as control (status): reason, separated by ;
Merged Without Approvaltrue when it merged although change management had not approved it
Review DueFor an emergency change, when its review is due
Risk Level, Risk ScoreThe risk assessment (score with one decimal)
In Blackouttrue when the risk assessment found it in a change freeze
Risk Heldtrue when the risk check held it
Change Approval Key, Change Approval StatusIts change approval and status
Earlier change approvalsHow many earlier change approvals it had (superseded or reopened)
Approved, Approved By, Approved AtThe approval
VotesEach vote as voter decision (source), separated by ;
Secret Scan, Secrets FoundThe secret scan's status and the number of possible secrets
Dependency Scan, New Vulnerabilities, Highest SeverityThe dependency scan's status, the vulnerabilities the merge request brings in, and the highest severity
Pipeline Status, Pipeline IDThe latest pipeline recorded on it

=== Changes Outside Change Management (N records) ===, one row per direct change: Detected, Repo (the project's path), Branch, Pushed By, Found By (push or head_check), Force Push, Branch Deleted, Commits, Commits Without MR, Before, After (the branch head before and after) and Commit Titles (of the commits not from a merge request, separated by |).

=== Audit Trail (N records) ===: Timestamp, Username, Action, Resource, Resource ID, Status, IP.

=== Job Processing Summary ===: Type, Total, Completed, Failed.

The PDF file​

A landscape A4 document with Page N of M and the generation time on every page:

  • First page: Compliance Evidence Report, the company, the period, and who generated it when, then the Summary: the total merge requests, a risk breakdown (low, medium, high, critical) of the merge requests included, the changes outside change management, the total audit entries, the job success rate (completed of all jobs), and a note for each part that was cut.
  • Merge Request Evidence: Repo, MR#, State, Author, Policy (name and version), Change, Gate, Risk, Change Approval Key, Change Approval Status, Approved By, Secrets (the scan status, or N found), Pipeline and Merged (the date). Long values are shortened with ..., by characters (a letter such as ş or ü is never cut in half). The Gate column flags merges the gate did not cover, in this order: BYPASSED (merged without approval), SOD BROKEN (separation of duties broken), IN FREEZE (merged in a change freeze), REVOKED (approval withdrawn after the merge); otherwise the gate.
  • Changes Outside Change Management: Detected, Repo, Branch, Pushed By, Found By, Forced, Deleted, No MR (commits without a merge request of all commits) and After.
  • Audit Trail and Job Processing Summary, with the CSV's columns.

An empty part says so (No merge request records found for this period., No change reached a branch under change management without a merge request in this period., No audit log records found for this period., No job records found for this period.).

Audit​

Every export is recorded as compliance_export (resource report): on success with the format, the period, the number of merge requests, audit entries and changes outside change management included and in total, and whether each was cut; on failure with the error. See Audit log.

API​

GET /api/v1/compliance/report streams the file.

ParameterValues
formatcsv (the default) or pdf
from, toYYYY-MM-DD (days in the company's time zone, to included) or RFC 3339 times. By default the last 30 days
date_basismerged_at (the default) or opened_at
company_idPlatform admins only, required for them

The answer's headers say what was included: X-Report-Truncated names the parts that were cut, comma-separated (merge_requests, audit_entries, direct_changes; empty when none was), and each part has its total and the number included: X-Report-Total-MRs and X-Report-Returned-MRs, X-Report-Total-Audit-Entries and X-Report-Returned-Audit-Entries, X-Report-Total-Direct-Changes and X-Report-Returned-Direct-Changes.

Policy managers and users get 403; a platform admin without company_id gets 400; a wrong format, date_basis or date gets 400.

Video tutorial

Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →

Audit Log and Compliance ReportYouTube ↗