# Commits Summary

## Overview

In AutoRABIT ARM, the **Commits Summary** screen provides detailed information about each commit or merge, including diffs of modifications. Commits are organized by the date they were made in ARM. By default, only commits by the logged-in user are displayed in reverse chronological order (most recent first).

## Accessing the Commits Screen

1. Navigate to **Version Control > Commits** to access the **Commits** screen.
2. For optimal viewing, set your browser's zoom level to **80%** (Chrome/Firefox).

## Viewing Commits

* To view all commits (including those by teammates), Click the **Created By Me** switch to the left.
* To filter commits pending reviewer approval, Click the **Pending Approvals** switch to the right.
* Use the search field to filter commits by Commit Type, Board, Created by and Created Range, revision number, or comment. *Note: Search is case-sensitive.*\ <br>

  <figure><img src="/files/THMgPjWimWGiJ4eXL2PW" alt=""><figcaption></figcaption></figure>

## Commit Details

Each commit entry displays:

* **Commit Type Initials**:
  * PV: Prevalidation Commit
  * EZ: EZ-Commit
  * M: Merge Commit
  * VM: Validate and Merge
  * BB: Branching Baseline
  * RC: Revert Commit
  * CI: Commit from CI Job
  * DR: Dry Run
  * EC: External Commit
* Commit label name
* Commit message
* Committer's username
* Commit creation date
* Version Control repository, destination, and source branch details
* Salesforce Org details (if applicable)
* Commit Revision label
* Commit/Merge status

## Quick Merge

Quick Merge allows direct merging from the Commits screen without navigating to the New Merge screen.

1. Hover over the three dots beside the desired commit.
2. Click **Quick Merge**.
3. Confirm the action in the pop-up.<br>

   <figure><img src="/files/12vUpIp0Zk2duXzpdRxL" alt=""><figcaption></figcaption></figure>

**Note:** Quick Merge is not available for:

* Prevalidation Merge commits pending approval
* Already merged commits

## Detailed View

1. Hover over the three dots beside a commit and click **Detailed View**.\ <br>

   <figure><img src="/files/mkBscWTLHKlQsjnKQ5OP" alt="" width="276"><figcaption></figcaption></figure>

The detailed view includes:

* Commit details
* Merge/EZ-Commit configuration
* Pull Request section (for EZ-Commits only)
* Reviewer comments
* Metadata diffs
* Deployment validation
* Code Analysis
* Logs and ALM integration\ <br>

  <figure><img src="/files/xF2VAQtTEB9mcSzCC70z" alt=""><figcaption></figcaption></figure>

  <br>

  <figure><img src="/files/sTUwQ3odYnBtsJiX6zfu" alt=""><figcaption><p>Visual display of Commit steps</p></figcaption></figure>

  <br>

  <figure><img src="/files/8V79soX5sTMPBW59q2YS" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/FOJlrgdGmthKllwMqJXC" alt=""><figcaption><p>Commit details Report panel</p></figcaption></figure>

## Code Analysis File

Static Code Analysis (SCA) is part of the security development lifecycle. Tools include ApexPMD, Checkmarx, Salesforce Scanner, and CodeScan. Violations are displayed by file and line<br>

<figure><img src="/files/a6hTt9hjxT3H89VnGyzv" alt=""><figcaption><p>Sample Static Code Analysis Report in EZ Commit details</p></figcaption></figure>

## Files Changed

ARM compares metadata changes between branches/orgs. RED indicates deletions or changes from the source; GREEN indicates changes in the destination.\ <br>

<figure><img src="/files/TggoTR6PSEgwcPBd8G92" alt=""><figcaption><p>Metadata Diff view</p></figcaption></figure>

<figure><img src="/files/YVuhgW3mrWghw7aASQPn" alt=""><figcaption><p>Inline diff and download options</p></figcaption></figure>

## Commit Status Types

* **Completed**: Successful commit/merge.
* **Failed**: Validation/deployment failed.
* **Merge Conflicts**: Conflicting files during merge.
* **Auto Rejected**: Review not completed in time.
* **Review Pending**: Awaiting reviewer action.
* **No Modifications**: No differences found.\ <br>

  <figure><img src="/files/f7pCjGve1Lgj8LL5mgD0" alt=""><figcaption></figcaption></figure>

## Filtering Commits

Filter options include:

* Repository and Branch
* Created by me
* All or Pending Approvals
* Pending Approvals
* Date Range
* Commit Type
* Created by
* Board (Salesforce or Vlocity)\ <br>

  <figure><img src="/files/Wj2omtSALE329vGePtrj" alt=""><figcaption></figcaption></figure>

## Delete Commits/Merges

Only users who created the commit or org admins can delete commits (unmerged only).

<figure><img src="/files/V7vGH7kATSVT2WrZM1iz" alt=""><figcaption></figcaption></figure>

**Note:**

* Deleted commits are not recoverable.
* An email notification is sent upon deletion.

## Commit Workspace

Parallel commits from the same source org to different VC branches are shown in the **Commit Workspace**. Users may remove commits queued for deployment.

<figure><img src="/files/wKGXR46THTErGckfNPaL" alt="Commit workspace showing queued commits"><figcaption><p>Commit queue overview</p></figcaption></figure>

## Deployment Workspace

Prevalidated deployments waiting in the queue are listed in the **Deployment Workspace**.

<figure><img src="/files/pLqV8AuC4EaNuUpOEBT3" alt="Deployment workspace with pending validations"><figcaption><p>Prevalidation queue view</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/version-control/ez-commits/commits-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.