# Usage ### A. Create Pre-validation Request Create a pre-validation request to commit from your local [version control](https://www.autorabit.com/7-tips-for-salesforce-version-control-integration/) repository.

Pre-validation request creation in VSCode Extension — Creating a pre-validation request

### B. Stage Changes #### Stage all changes

Staging all changes in VSCode Extension — Stage all changes

#### Stage changes for a file

Staging changes for a single file in VSCode Extension — Stage changes for a file

#### Stage selective line of code

Staging selected lines of code in VSCode Extension — Stage selective line of code

### C. Submit Pre-validation Request While submitting the pre-validation request, you may choose the following criteria as pre-checks: 1. Generate Diff Report 2. Run Static code analysis 3. Validate deployment #### Generate Diff report AutoRABIT compares the metadata between the source org and the destination branch and generates a metadata difference report. The diff report shows a summary of metadata component differences between the org and the branch. #### Run Static code analysis [Static code analysis](https://www.codescan.io/blog/what-is-salesforce-static-code-analysis/) detects data flow problems, software defects, language implementation errors, inconsistencies, dangerous usage, coding standard violations, and security vulnerabilities, if any. #### Validate Deployment AutoRABIT performs a check-only deployment to your selected org/branch. Nothing is deployed; however, if the deployment fails or tests do not pass, the issues will be clearly shown so they can be resolved.

Pre-validation request options in VSCode Extension — Submit pre-validation with selected checks

### D. Commit approved pre-validation request Commit the code once the pre-validation request has been approved.

Committing approved pre-validation request in VSCode Extension — Commit approved request

### E. View Pre-validation Requests #### Diff Report

Viewing diff report in VSCode Extension — Diff Report

#### Static Code Analysis Report

#### Validate Deployment Report

Viewing deployment validation report in VSCode Extension — Validate Deployment Report

### F. Trigger Build This extension also allows developers to trigger builds once the code is committed. Actions like Quick Deploy and Abort are available for each build.

Triggering builds using VSCode Extension — Triggering a build

### G. Deployments Use the extension to view results for pre-validations, builds, and deployments.

Viewing deployment results in VSCode Extension — Viewing deployments

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://knowledgebase.autorabit.com/product-guides/arm-1/integration-and-plugins/visual-code-extension/working-with-vscode-extension.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.