> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/version-control/change-labels/commit-labels.md).

# Commit Labels

### Commit Labels: Overview <a href="#commit-labels-overview" id="commit-labels-overview"></a>

A Commit Label helps to label a commit. For example, changes related to a user story or task, etc. can be placed under a specific label. The main advantage of creating a commit label is to reuse the labels and perform many commits under it.

### Creating a Commit Label <a href="#creating-a-commit-label" id="creating-a-commit-label"></a>

1. Log in to your AutoRABIT account.
2. Hover your mouse over the [**Version Control**](https://www.autorabit.com/blog/7-tips-for-salesforce-version-control-integration/) module and click on the **Change Labels > Commit Labels** or go directly to the **Change Labels** tab and select **Commit Labels** from the dropdown.The **Commit Labels** screen is best viewed when the zoom setting is set to **75%** on your Chrome/Firefox browser.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FBfgr00LO61iF5GO7SD9f%2Fimage.png?alt=media&amp;token=51b637bb-2e82-43f4-a43e-243fc906a3d7" alt="" width="225"><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F2yCCwaAKH3QrNG96YrhD%2Fimage.png?alt=media&amp;token=d5b7256d-7dbc-4b07-a78b-f6ee0781658c" alt=""><figcaption></figcaption></figure>

3. Next, click on **Create Commit Label** button.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FsrcWFurvnHQh66wpNmax%2Fimage.png?alt=media&amp;token=1b9a69b4-257e-4ca7-8690-be0063ca0b50" alt=""><figcaption></figcaption></figure>

4. On the next dialog box that appears, give the commit label a **name** for your reference. Also, include brief information about the label created in the **Description** box. Select your **VC** **Repository**, its mapped **Branch,** and the **Label Type** for which you want to create a commit label.
5. Click **OK**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Ft5Nrrg2Gx4lutdS2bZtC%2Fimage.png?alt=media&amp;token=24b99863-c754-4512-8b4a-c0a059c04d99" alt=""><figcaption></figcaption></figure>

6. The commit label will be displayed under the **Commit Label** tabs along with other commit labels.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fs38PSmg48ldwU6wnWgCb%2Fimage.png?alt=media&amp;token=8d6f1dbf-4fe7-4ba8-ab1a-95ada1179cc5" alt=""><figcaption></figcaption></figure>

7. Now, whenever you perform a merge or commit using the previously created commit label, a revision number generates. These revision details are available on the right side of your commit label.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FxxyPzSsClcBVO2qciOst%2Fimage.png?alt=media&amp;token=60070b66-4828-4b92-a8fe-fb2709752623" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYNml65PpqiRSMw4Buxwx%2Fimage.png?alt=media&amp;token=36c862a9-d67a-48b5-95e5-385b89029284" alt=""><figcaption></figcaption></figure>

8. Click on the **...** icon to view detailed info about the revision of the commit label created. The info includes revision creation date, revision committed by, revision number, and components.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtUSnlKOPl23uo7UKshWU%2Fimage.png?alt=media&amp;token=74f174a2-8c60-46b3-86d1-9980aabf0ce6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPcsCdFgQeQrcBRLFXmFx%2Fimage.png?alt=media&amp;token=7472c5d6-ec2f-4a5f-81b2-414cd13bdfd6" alt="" width="359"><figcaption></figcaption></figure>

### Filtering the Commit Labels <a href="#filtering-the-commit-labels" id="filtering-the-commit-labels"></a>

Use the **Advanced Search** filter option to fetch any specific commit label faster.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FQfhje1EAXQ9zbuvIfZfE%2Fimage.png?alt=media&amp;token=4269b268-63a1-4896-a726-dff4074d7a71" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FslIvzXMRcmMtrbAWECnd%2Fimage.png?alt=media&amp;token=0e7af706-c42a-46fa-b6ea-0bed7d2e37e4" alt=""><figcaption></figcaption></figure>

Filter the commit labels via:

1. **Branch:** Filter the commit labels based on the Version Control Repository/ Branch for which the commit label is registered.
2. **Label Type:** Filter the commit labels by Label type, e.g., Salesforce Label or Vlocity Label.
3. **Label:** Filter the commit labels by name.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/arm-features/version-control/change-labels/commit-labels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.