> 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/release-labels/select-all-revisions-in-release-labels-classic-ui.md).

# Select All Revisions in Release Labels (Classic UI)

**Product:** AutoRABIT ARM\
**Module:** Version Control – Release Labels\
**Availability:** Classic UI

### Overview

AutoRABIT ARM has enhanced the **Release Label creation and update workflow** in Classic UI by introducing a new **Select All** option.

This enhancement allows users to select or deselect all available revisions with a single click, eliminating the need to select each revision individually.

### What's New?

#### Select All Revisions

The following capabilities are now available when creating or updating Release Labels:

* **Select All:** Selects all available revisions in the list with a single click.
* **Deselect All:** Unchecking the Select All checkbox clears all selected revisions.
* **Individual Selection:** Users can continue to select or deselect specific revisions based on their requirements.
* **Create and Update Support:** The option is available when creating new Release Labels and editing existing ones.

### How to Use

1. Log in to AutoRABIT ARM using the **Classic UI**.
2. Navigate to **Version Control > Release Labels**.
3. Create a new Release Label or edit an existing one.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fn59YWJYxY3p9NUkxVnbF%2Fimage.png?alt=media&amp;token=74205d95-14b9-4fa7-b8ef-8315a93b8dcb" alt=""><figcaption></figcaption></figure>

Complete the required Release Label configuration and navigate to the revision selection section.

4. Select the **Select All** checkbox to select all available revisions.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzMSqrQKgWf5nNkXTZcS8%2FScreenshot%202026-11-06%20at%2023.24.38.png?alt=media&amp;token=98034acf-86b0-426f-b1f9-f5b97b32c00c" alt=""><figcaption></figcaption></figure>

6. Uncheck **Select All** to clear the selection, or select and deselect individual revisions as needed.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FH4md8hrw2ufCpAWPmK3e%2Fimage.png?alt=media&amp;token=dc501986-d374-429c-ab4b-2c7dd84029fc" alt=""><figcaption></figcaption></figure>

7. Review the selected revisions and save the Release Label.

### Important Notes

* The Select All option is available for both creating and updating Release Labels.
* Unchecking Select All deselects all currently selected revisions.
* Users can continue to manage individual revision selections.
* The existing Release Label configuration and management process remains unchanged.
* This enhancement is supported in the **Classic UI**.

### Benefits

* Reduces manual effort when selecting multiple revisions.
* Simplifies Release Label creation and updates.
* Provides flexibility to manage revisions individually or in bulk.


---

# 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/release-labels/select-all-revisions-in-release-labels-classic-ui.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.
