---
schema_version: "1"
id: 09933be72535a4fe6941e7540b9f279bce31de7f97c3bcee2f2275d0a5494c96
title: Merging Branches
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/design-center/design-ghs-merge-branches.md
canonical_url: https://docs.mulesoft.com/design-center/design-ghs-merge-branches
source_site: docs.mulesoft.com
content_type: documentation
content_hash: fd4847f378dd2395321a4a446a6b010cbbcdd3465b9db62ec28e08cfe7c846a5
description: MuleSoft Documentation Site
latest: true
---
---
product: Design Center
---

# Merging Branches

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When you merge branches, you combine a target branch with changes from a forked source branch, often
called a _feature branch_. The target branch reflects these changes, and the source branch remains
unmodified. You can merge branches within the API Designer interface.

## Merge A Branch

1.  In the Design Center **Projects** list, click a project name to open the text editor. The
    **Merge** button appears next to the branch selector component button (if branches have already
    been created).

2.  Click Merge.

3.  In the **Merge branch** dialog, select the target branch in the dropdown list of branches.

4.  Expand **Advanced Settings**.

5.  Select **Squash commits**.

    Squashing commits compacts the source branch’s commits into a single commit for merging and
    keeps the target branch’s commit history clean and concise.

6.  To automatically delete the source branch after merging, select **Delete branch**.

7.  Click **Merge**.

    After merging, the merge target branch becomes the current branch.

## Resolving Merge Conflicts

Merge conflicts arise when either the source branch or the target branch contain changes (commits)
that are not in the other branch. When merge conflicts occur, you must choose which branch to bring
forward. You can specify the source branch or the target branch.