> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/code.md).

# Code

- [Overview of Branches](https://docs.flosum.com/devops/code/overview-of-branches.md): View and manage all branches in your Flosum project.
- [Managing Branches](https://docs.flosum.com/devops/code/managing-branches.md)
- [Creating a Branch](https://docs.flosum.com/devops/code/managing-branches/creating-a-branch.md): Create a new branch from an existing source branch to manage isolated development work.
- [Branch Actions](https://docs.flosum.com/devops/code/branch-actions.md)
- [Adding Components to a Branch](https://docs.flosum.com/devops/code/branch-actions/adding-components-to-a-branch.md)
- [Adding Pre and Post Destructive Changes to a Branch](https://docs.flosum.com/devops/code/branch-actions/adding-pre-and-post-destructive-changes-to-a-branch.md): Use destructive changes to remove Salesforce metadata components during deployment. You can configure them as Pre or Post to control when the deletions happen.
- [Using Smart Merge](https://docs.flosum.com/devops/code/branch-actions/using-smart-merge.md)
- [Resolving Smart Merge Conflicts](https://docs.flosum.com/devops/code/branch-actions/resolving-smart-merge-conflicts.md)
- [Using Branch PreDeploy Fix](https://docs.flosum.com/devops/code/branch-actions/using-branch-predeploy-fix.md): PreDeploy Fix proactively detects and resolves missing dependencies before deployment.
- [Using Branch Overwrite Protection](https://docs.flosum.com/devops/code/branch-actions/using-branch-overwrite-protection.md): Overwrite Protection is a safeguard process that runs against a Salesforce org to prevent accidental overwrites of metadata.
- [Using Branch Validate](https://docs.flosum.com/devops/code/branch-actions/using-branch-validate.md): Validate checks your branch metadata against a Salesforce org without deploying. It confirms compatibility, ensures dependencies are satisfied, and runs Apex tests if required.
- [Deploying a Branch](https://docs.flosum.com/devops/code/branch-actions/deploying-a-branch.md): Deployment pushes your branch’s metadata components into a target Salesforce org. It actually applies changes, making it the final step in moving code/config into Salesforce environments.
- [Rolling Back a Deployment](https://docs.flosum.com/devops/code/branch-actions/rolling-back-a-deployment.md): Rollback lets you restore a Salesforce org to its pre-deployment state. It creates a backup automatically, so if errors or unwanted changes occur, you can quickly return the org to stability.
- [Code Tools](https://docs.flosum.com/devops/code/code-tools.md)
- [Using AI Test Class](https://docs.flosum.com/devops/code/code-tools/using-ai-test-class.md)
- [Using AI Code Documenter](https://docs.flosum.com/devops/code/code-tools/using-ai-code-documenter.md)
- [DevOps CLI](https://docs.flosum.com/devops/code/devops-cli.md)
- [Overview of DevOps CLI in VS Code](https://docs.flosum.com/devops/code/devops-cli/overview-of-devops-cli-in-vs-code.md)
- [Installing Flosum CLI Node.js Package](https://docs.flosum.com/devops/code/devops-cli/installing-flosum-cli-node.js-package.md)
- [Installing Flosum DevOps-CLI Extension](https://docs.flosum.com/devops/code/devops-cli/installing-flosum-devops-cli-extension.md)
- [Using DevOps CLI in VS Code](https://docs.flosum.com/devops/code/devops-cli/using-devops-cli-in-vs-code.md)
- [Updating Flosum CLI and DevOps-CLI Extension](https://docs.flosum.com/devops/code/devops-cli/updating-flosum-cli-and-devops-cli-extension.md)


---

# 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://docs.flosum.com/devops/code.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.