Skip to main content
Git integration is an enterprise capability that stores pipeline definitions in a Git repository alongside application code. You get pull requests, diff review, rollback, and alignment with existing SDLC practices.
Git integration is included on enterprise editions. Your administrator configures the Git host, repository access, branch protections, and which artifacts Planasonix reads and writes (for example, graph definitions, variable metadata, and companion docs).
Supported providers, sync direction, and conflict behavior can vary by tenant. Confirm the exact mapping with your platform team before you rely on Git as the sole source of truth.

​
What you gain

  • Collaboration: Propose changes in branches; reviewers comment on graph diffs the same week they review services.
  • Auditability: Every merge records who changed which node configuration and when.
  • Recovery: Revert a bad deploy by checking out a known-good commit and syncing back to Planasonix.

​
Push and pull

ActionWhen you use it
PushPublish canvas changes from Planasonix to the remote branch after you finish an edit session.
PullBring remote commits into Planasonix when teammates merged updates or when CI generated changes.
Workflow tips:
  • Push before opening a PR if your team treats Planasonix as the authoring surface of record.
  • Pull at the start of a session if developers sometimes edit exported definitions in the repo (discourage concurrent edits in both places without coordination).
Conflicts can occur if the same pipeline changes in Git and on the canvas without syncing. Establish a single primary editor per branch, or use a short-lived branch per change.

​
Status and history

The Git panel shows:
  • Branch and remote you are bound to.
  • Ahead / behind counts relative to the default integration branch.
  • Last sync time and any errors from the provider (permissions, large files, hook failures).
History lists commits that touched pipeline artifacts. Click through to your Git host for full blame and compare views.

​
Branch management

1

Create a working branch

Branch from your integration branch (main, develop, or your org standard) before large refactors.
2

Author in Planasonix or locally

Edit on the canvas, or—if supported—edit checked-out files in your IDE. Keep commits small and message them with intent (“fix join key on orders”).
3

Push and open a pull request

Use your Git host’s PR workflow. Attach run evidence (screenshots of preview, sample metrics) when behavior changes.
4

Merge and deploy

After merge, sync Planasonix with the integration branch and promote through environments if applicable.

​
PR validation

Many organizations attach checks to pipeline PRs:
  • Schema diff warnings when destination columns change.
  • Policy checks that block new nodes without owners or data classification.
  • Dry-run jobs that execute against a sandbox warehouse on a sample partition.
Planasonix may expose webhook or API hooks so your CI can trigger validation when PRs touch pipeline paths—coordinate with your platform admin for the exact integration.

Environments

Pair Git merges with staged rollouts.

Variables

Keep secrets out of Git; use variables and secret stores.