> For the complete documentation index, see [llms.txt](https://docs.nected.ai/nected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nected.ai/nected-docs/development-lifecycle/git-based-source-control/merge-and-deploy.md).

# Merge & Deploy

Merging ensures that any updates committed and reviewed in your Git repository become available inside your Nected workspace. While Nected manages commits, pushes, pulls, and conflict resolution at the workspace level, **all merge requests (PRs/MRs) are handled outside Nected by GitHub**.

## **How Merging Works?**

#### **1. Push from Nected**

A user commits and pushes changes from the Nected UI into the selected branch in Git.

#### **2. Open a Pull Request in GitHub**

To merge these changes into your production or base branch (typically `main` or `master`), your team must create a pull request directly in GitHub.

{% hint style="info" %}
Read the GitHub doc on how to set a PR and merge the changes to production: <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests>
{% endhint %}

GitHub handles:

* Code review
* Branch protection rules
* Required checks (CI/CD)
* Merge approvals
* Conflict resolution

#### **3. Merge the Pull Request in GitHub**

Once the PR is approved and merged:

* GitHub updates the branch’s commit history
* The branch now represents the authoritative version of the logic

#### **4. Pull Changes into Nected**

Return to Nected and click **Pull** to import the latest merged state.

During the pull, Nected will:

* Check for incoming changes
* Sync integrations and credentials
* Update missing configs
* Apply the merged logic and versions
* Resolve workspace-level conflicts (Override, Archive, Merge & Pull)

Your workspace now reflects the new merged branch state.


---

# 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.nected.ai/nected-docs/development-lifecycle/git-based-source-control/merge-and-deploy.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.