> 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/branch-actions/adding-components-to-a-branch.md).
# Adding Components to a Branch
##  Overview
When a branch is first created, its Components tab contains metadata inherited from the Main Branch or from the source branch used during creation. You can add more metadata at any time using the Add Components button.
{% hint style="info" %}
#### Best Practices
* Always add components from the correct Salesforce org to avoid mismatches.
* Review Activities for conflicts before proceeding with pull requests or merges.
* Keep commit messages meaningful so you can track why specific components were added.
{% endhint %}
## Adding Components
{% stepper %}
{% step %}
### Select a Branch
1. Click **Branches** from the left sidebar menu.
2. Select a branch from the list.
{% endstep %}
{% step %}
### Add Components
1. Click **+ Add Components**.
2. Click **Select** for the Salesforce organization you want to retrieve metadata from.
3. Click **Next**.
4. Use the **Search**, **Filter**, and **Sort** options to find the components to add.
5. Click the **+ Select** button for each component to add.
6. Click **Next**.
{% endstep %}
{% step %}
### Commit Changes
1. Enter a commit message in the text box.
2. Click **Commit**.
3. After committing, the **Activities** tab will show the **Commit To Branch** job you just started.
4. Once the job is complete, switch to the **Components** tab to see the components you added.
{% endstep %}
{% endstepper %}
---
# 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/branch-actions/adding-components-to-a-branch.md?ask=&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.
