> For the complete documentation index, see [llms.txt](https://docs.neurelo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neurelo.com/guides/remote-git-repository-for-definitions/syncing-branches.md).

# Syncing Branches

By default, the project will use the branch specified as the "Default Branch" when connecting the Remote Git repository to the project.&#x20;

### Branch Setup

* You can sync an existing branch from the repo or create a new branch in Neurelo by using the Branch selector and clicking on the “New branch”

<figure><img src="/files/GW2qTkLu2LN1wYMy9VMT" alt="" width="563"><figcaption></figcaption></figure>

* You can enter the name of the branch and “Submit”

<figure><img src="/files/hIyL8EUkqNlFNGh0jHFD" alt="" width="375"><figcaption></figcaption></figure>

* This will pull the branch from the remote git repository if it is found; or otherwise, create a new branch off the default branch.
* New changes will be pulled every 5 minutes, or you can manually pull the changes by clicking on the “Sync” button.

### Manual Sync

Once you push new commits to your branch, you can sync those changes in Neurelo by clicking on the “Sync” button.

* For example, let’s say we have a branch named `feature-1` at commit `8a9731...9f6553`

<figure><img src="/files/JAMIDAb3LE6Gf374H3J7" alt="" width="563"><figcaption><p>Commit History in Neurelo</p></figcaption></figure>

<figure><img src="/files/Fg9X1EOspMaFyzme09ZP" alt="" width="563"><figcaption><p>Commit History in GitHub</p></figcaption></figure>

* If we push commits to the branch on the remote git, they will appear in the repository’s commit history. The new commit here is `f7559f8`.

<figure><img src="/files/X90V9moVWh6Nr1dl4yBN" alt="" width="563"><figcaption></figcaption></figure>

* Then, we can go to Neurelo and click on Sync for the `feature-1` branch. This will start a sync in the background and pull the new commit.

<figure><img src="/files/3nEnUaRhB4ownyFBJwf2" alt="" width="563"><figcaption></figcaption></figure>

* If we open the Commit History in Neurelo, we see that the “new commit” with the same commit ID as GitHub appears.

<figure><img src="/files/98ArzpaxYT65YXL2sVaH" alt="" width="375"><figcaption></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.neurelo.com/guides/remote-git-repository-for-definitions/syncing-branches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
