> 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-1/getting-started-1/registration/version-control-repository/update-repository-remote-url-in-version-control-repositories-new-ui.md).

# Update Repository Remote URL in Version Control Repositories (New UI)

**Product:** AutoRABIT ARM\
**Module:** Admin – Version Control Repositories\
**Availability:** New UI\
**Access:** Registered Organization Super Admin only

### Overview

AutoRABIT ARM now allows **Super Admins to update the remote URL of an existing Version Control repository** directly from the repository Details screen.

This enhancement simplifies repository management when a repository URL changes due to repository migration, organization renaming, or switching between HTTPS and SSH connections, eliminating the need to contact AutoRABIT Support for manual updates.

### What's New?

#### 1. Update Repository URL

* A new **Edit** option is available next to the Repository URL in the **Details** tab.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F8tty33TiQgUQyf7IeGiz%2Fimage.png?alt=media&amp;token=3962e2cf-dfea-4e7b-834d-c5d807790cdc" alt=""><figcaption></figcaption></figure>

* Clicking Edit opens an **Update Repository URL** dialog displaying the current URL and allowing users to enter a new URL.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLYJT9okLlsilBXU9FD0H%2Fimage.png?alt=media&amp;token=4f02651d-efbc-46e0-8f74-751b4df2c339" alt=""><figcaption></figcaption></figure>

* ARM validates the new URL to ensure it is valid, different from the existing URL, and not already registered with another repository.

#### 2. Confirmation and Update Status

Before updating the URL, ARM displays the following confirmation message:

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVe7n14KX2b9EvKv2Tbv4%2Fimage.png?alt=media&amp;token=4fcde617-1308-48a1-8371-b17470df06f8" alt=""><figcaption></figcaption></figure>

**"Ensure no users are performing any actions or have any pending tasks on this repository before you change its URL."**

Once confirmed:

* ARM processes the URL update in the background.
* A loading indicator appears while the update is in progress.
* Upon completion, ARM displays a **Success, Warning, or Error** message based on the outcome.
* The repository list is refreshed to display the updated URL.

#### 3. Automatic Reference Updates

ARM automatically updates the repository URL across associated configurations and records, including user mappings, Version Control settings, commit labels, CI jobs, merge history, and pull request history.

This helps maintain consistency across existing repository references.

### How to Update a Repository URL

1. Log in to AutoRABIT ARM as the **Registered Organization Super Admin**.
2. Navigate to **Admin > Version Control Repositories**.
3. Select the required repository and open the **Details** tab.
4. Click the **Edit** icon next to the Repository URL.
5. Enter the new URL in the **Update Repository URL** dialog.
6. Review the confirmation warning and ensure no active or pending operations exist for the repository.
7. Confirm the update and wait for the operation to complete.
8. Once completed, verify the updated URL in the repository details.

### Important Notes

* Only the **Registered Organization Super Admin** can update repository URLs. Standard Admins and other users cannot access this option.
* The new URL must not be empty, contain spaces, match the existing URL, or already be registered with another repository.
* Ensure there are **no active or pending operations** on the repository before initiating the update.
* Only one repository rename or URL update operation can run at a time within an organization.
* If an update is already in progress, the Edit option remains unavailable until the operation completes.
* If the repository URL has changed since the page was loaded, ARM requests that the user refresh the page before proceeding.
* If the update completes with partial failures, ARM displays a warning. The same update can be submitted again to complete the remaining changes.
* Existing local Git workspaces are not updated immediately. Subsequent checkouts use the updated repository URL.
* Repository URL update activities and outcomes are recorded under **Admin > Audit**.

### Benefits

* **Self-Service Management:** Allows Super Admins to update repository URLs without Support intervention.
* **Reduced Manual Effort:** Automatically updates associated repository references.
* **Improved Visibility:** Provides real-time progress and completion status.
* **Controlled Updates:** Includes validation, confirmation, and access restrictions.
* **Better Traceability:** Records repository URL changes in audit logs.


---

# 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-1/getting-started-1/registration/version-control-repository/update-repository-remote-url-in-version-control-repositories-new-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.
