> For the complete documentation index, see [llms.txt](https://docs.devin.fm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devin.fm/guides/modules/branch-a-module.md).

# Branch a Module

One of the core [version control](/features/version-control.md#devins-approach-to-version-control) features in Devin is the ability to branch files for different purposes through its development cycle. When branching a file, Devin will create a copy of the file so that development, testing or other activities are performed on a separate isolated copy of the original file.

To branch a file:

1. Go to the Branches view
2. Select the branch that you want to branch out from
3. Click the three dots and click Branch
4. Enter a branch name or choose an existing one.
5. Click the reload icon to see the branched file on the branch list 

## Video Tutorial

{% embed url="<https://vimeo.com/938585801?share=copy>" %}
Branching a Module
{% endembed %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devin.fm/guides/modules/branch-a-module.md?ask=<question>
```

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.