Commit & Push

Nected’s Git Sync lets your team capture every change to Rules, Workflows, Datasets, Integrations, and Variables in Git. Commits are created directly from the Nected workspace, while code reviews, PR approvals, and merge conflict handling continue to be managed in Source Control.

This ensures a clean separation of responsibilities:

• Nected → Create commits, push changes, view diffs, track modifications

• Source Control Repo→ Review pull requests, validate changes, enforce branch protection, resolve conflicts, merge branches

Together, they provide a controlled, auditable workflow for decision automation development.

What Gets Tracked in a Commit

Every commit created from Nected includes the exact set of modified resources since the last push:

Tracked Resource Types

• Rules (Simple Rules, RuleSets, Versions)

• Workflows (nodes, triggers, nested workflows)

• Integrations (config changes, added connections)

• Datasets (schema updates, structure changes)

• Variables & Secrets (non-sensitive metadata only)

• Schedulers / Cron Triggers

Credentials are never synced for security reasons.

Pushing Changes (Commit & Push)

You can push changes either from the workspace-level push panel or from an individual rule/workflow editor.

1. From the Workspace Push Panel

1. Click Push in the bottom-left corner

2. Nected loads all pending changes since the last deploy/pull

3. You will see a summary like the screenshot.

4. Enter a commit message

5. Choose your commit method:

Commit Options

Option	Behavior
Commit and Push	Creates a standard commit and pushes to the remote branch
Force Push (Override and Push)	Replaces the remote branch version with your local workspace version

2. From an Individual Rule or Workflow

Inside a Rule or Workflow editor:

1. Click the ⋮ (more options menu)

2. Select Push to Git

3. Nected opens a push dialog scoped to that specific resource

4. Enter a commit message and push

This is useful when you want to commit one rule or workflow without touching workspace-wide changes.

Handling Push Conflicts

If Nected detects that your local workspace differs from GitHub:

Your options:

• Override and Push → Force your local changes into GitHub

• Discard Changes → Cancel the operation

GitHub remains the authority for merging logic. Nected does not handle conflict resolution itself. If the conflict requires code-level resolution, you must:

Resolve the conflict inside GitHub → Commit → Pull into Nected

Reviewing Changes (In GitHub)

Reviewing, approving, and merging changes into target branches is performed in GitHub, not in Nected.

This includes:

• Opening pull requests

• Reviewing diffs

• Adding comments

• Approving or rejecting PRs

• Checking CI/CD workflows (if configured)

• Enforcing branch protection rules

• Resolving merge conflicts

Nected only handles the commit creation and syncing, while GitHub remains the system of record for code review.

Once a pull request is merged:

1. Nected users click Pull

2. The updated state from GitHub is imported into the workspace

3. Local workspace items update accordingly

Best Practices for Commit & Review

• Commit small, isolated changes for cleaner diffs

• Use meaningful commit messages (e.g., “Add discount eligibility rule logic”)

• Always pull before starting new work to reduce conflicts

• Never bypass GitHub reviews if your team uses branch protection

• Use feature branches for experimental or risky logic