Skip to main content
AutoRABIT, Inc.

New EZ-Commit

How to commit your changes from Salesforce org to Version Control?

Committing is a relatively straight forward process that adds your changes to the history of your repository and assigns a commit name to it.



The following pre-requisites are required to use commit functionality:

  1. User has permission to perform EZ-Commits.
  2. Salesforce Org Registered with AutoRABIT.
  3. Version Control Registered with AutoRABIT.
  4. My Profile is mapped with user details for Salesforce Org as well as Version Control.



  1. Log in to your AutoRABIT account. Go to your Version control and then click on New EZ- Commit.
  2. On the next pop up screen select a source Salesforce org from the list.
  3. Next, select the Author from the list. Based on the org that you have selected; the list of mapped users will be displayed.
NOTE: There is also a provision to select All in Author field. This option is used to commit changes
across the orgs irrespective of the user. It is accessible only to AutoRABIT org admin.

  1. In case you want to commit that were authored between any two dates, click on Filter option.
  2. Next click on Additional Metadata. Additional Metadata allows you to select the Metadata Members from Salesforce Org and commit them. When multiple users make changes to metadata, the last modified date of a Picklist is not updated by Salesforce, so AutoRABIT provides an option to include pick lists.
  3. Select the Metadata Type from the drop-down field. You can select the required metadata members here and commit them.


  1. For multi-picklist, select Picklist from the Metadata Type field. Next choose an object and click Add button. For the selected object, all the existing metadata members will get displayed.
  2. Next, click OK.


  1. Clicking on Fetch Changes will allow you to see live status updates about the changes that are being fetched from a Salesforce Org.
  2. All the metadata types that have been modified/ added will get displayed.

  1. Next, choose a Label Type.
    1. Custom Label - Custom Label helps to label a commit. For ex: Changes related to a user story or task etc., under a specific label. These changes can be picked and deployed into various orgs using the label provided from “Start new build” option in the build home page. You can re-use the labels and perform multiple commits under a given label. Select the label from the dropdown or create a new one by clicking “+” icon.
    2. Release Label - Release label is the label created by grouping your EZ-commit labels as a release label.
    3. ALM System - Once the changes are committed to the version control system, the status of the ALM work item is updated and reflected in your ALM system. Once you proceed with ALM System as Label Type, you need to execute the below steps:
      1. Select the ALM type from the drop-down box. Currently AutoRABIT supports ALM types like Jira, IBMRTC, Version One, and CA Rally.
      2. Select the Project and the Planned for from the drop-down list for which the commit is planned.
      3. Click Go.

  1. Next, Select the Work item and the status from their respective fields.

  1. At last, click on either:
    1. Validate & Commit - validate the changes before committing to ensure the commit will succeed.
    2. Compare & Commit - compares the metadata between the source and destination orgs before committing.
    3. Commit - allows only to commit to Version Control System.
Note: A user can exercise Compare & Commit and Commit options only if the permission is authorized for the user’s active role. 
If not permitted, the user can view Validate & Commit option only. Refer to Role Management Section for more details.




Validate & Commit Changes

Validate & Commit allows you to validate your commit before committing to any Version Control System to ensure the commit will succeed. The results display all the errors and warnings that an actual commit would. This feature even allows you to generate reports before commit such as Static code analysis, code coverage, validate deployment with success, warning and errors, etc.


  1. Repeat the steps 1-12 in the Procedure section under How to commit your changes from Salesforce org to Version Control.
  2. Next, enter a name in Commit Label name field (no special characters are allowed).
  3. Choose a Salesforce Org from Validate on Salesforce Org drop down field.
  4. Additional options:
    1. Show Code Level Differences (mandatory): If checked, it will generate code level difference report between two orgs. You can view the report in Commit Validation History homepage.
    2. Run Static Analysis (optional): Generates Pre-validation static analysis report. To view the report, go to Version Control > Commit Validation History.
    3. Run Apex Tests Dynamically (optional): Generates apex tests report. To view the report, go to Version Control > Commit Validation History.
  5. You can also add Apex Test Classes manually. To add, enter the test classes separated by comma and click on Add button.
  6. Enter the Reviewer Email Id(s) and comment in their respective field.
  7. Next, check Commit Profiles/Permission sets only for the selected metadata if required.
  8. Click Proceed for Validation.
Note: You can view a list of all commits that is pre-validated before committing to Version Control System in
Commit Validation History section. To view, go to Version Control > Commit Validation History.​​​​


Compare and Commit changes

AutoRABIT allows you to compare the changes between the source and destination orgs before committing and generates a difference report.

  1. Repeat the steps 1-12 in the Procedure section under How to commit your changes from Salesforce org to Version Control.
  2. Next, click on Compare and Commit.
  3. On the next screen, click on the Difference icon to see the difference report between the source and the destination org.
  • Was this article helpful?