> 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/troubleshoot/best-practices/prerequisite-while-performing-a-commit-using-autorabit.md).

# Commit Prerequisites

Complete the following steps before starting a commit operation in AutoRABIT:

1. **Register Your Version Control Repository**
   * Only an administrator can perform this step.
   * Register your version control system (e.g., **Git**, **SVN**, or **TFS**) in AutoRABIT.
2. **Register Your Salesforce Organization**
   * Connect AutoRABIT to your Salesforce Org using **OAuth** or **username/password** authentication.
   * This step requires admin-level access.
3. **Set Up a Branch**
   * Create a feature branch to isolate changes instead of editing the main code base directly.
   * This operation must be performed by an administrator.
4. **Map Users to Version Control and Salesforce Orgs**
   * In the **My Profile** section, map users to the registered Salesforce Orgs and version control repositories.
   * Assign necessary permissions to allow project creation in AutoRABIT.


---

# 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/troubleshoot/best-practices/prerequisite-while-performing-a-commit-using-autorabit.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.