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.

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

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.