Branches

Branches in Nected allow teams to work in parallel without affecting production. Every Rule, Workflow, Dataset, Integration, and Variable you create or modify is isolated to the currently selected Git branch until you commit and push your changes.

When connected to GitHub, Nected automatically imports your repository’s branch structure and lets users switch to any branch they have permission to access.

How Branch Access Works?

Branch visibility in Nected fully depends on the user’s GitHub permissions:

Workspace Owner / Repository Owner

• Sees all branches from the connected repository

• Can push and pull on every branch

• Can select any branch as default

Workspace Members with Limited Access

• Only see branches they have explicit GitHub permissions for

• Can push/pull only on those authorized branches

• Cannot access protected or restricted branches unless granted permission in GitHub

This ensures that GitHub remains the single source of truth for branch security and governance.

Understanding Branches

Branches allow multiple developers and product teams to work independently without overwriting each other’s logic. Nected stays in sync with GitHub’s branch model, ensuring that:

• Feature development happens safely in non-production branches

• Testing can occur on isolated rule/workflow versions

• Merges remain controlled via GitHub

• Production changes only occur through the default branch

Switching Branches

You can switch branches directly inside Nected.

To switch branches:

1. Open the branch dropdown in the bottom-left workspace sidebar

2. View the list of branches you have access to

3. Select your desired branch

4. Nected loads the content of that branch

Once the workspace finishes loading, you will see:

Available Git configurations:

Setting	Description
Repo Name	Link of the connected GitHub repository
Default Branch	Currently active branch. Along with that, using the dropdown, you can change the active branch
Personal Access Token	You can edit the token in case the current token is expired.

Protected branches enforce Git workflows by disallowing direct changes in Nected unless changes come through GitHub merge events.