Skip to main content
Git-based version control enables to track and manage changes to workspace configuration in a Git repository. Workspace configuration changes include changes to connections, jobs, pipelines, and transformations. Version control is configured per workspace. Each workspace is associated with its own repository and operates independently from other workspaces.
Git version control requires an Enterprise license.
For details about setting up version control, see Git Version Control Configuration.

​
Using Version Control

When you enable version control, stores your workspace configuration in a Git repository and tracks changes to that configuration over time. With version control, you can perform the following actions:
  • commit and push configuration changes to a remote repository
  • pull updates from the repository into the workspace
  • view your commit history and inspect differences
  • restore configuration from previous commits
These operations are performed in the interface.

​
Accessing Version Control

Git version-control features are available in the following locations in the UI:
  • Settings > Git Version Control: You can configure the repository connection, authentication, and branch.
    • Note: In this case, Settings is the workspace settings (icon in the left navigation pane), not the system settings (gear icon in the upper right of the window).
  • Footer status bar: You can view pending changes, commit and push updates, pull remote changes, and view the current branch.
  • Activity > Commit History: You can view commit history, inspect changes, and restore previous configurations. Selecting a commit on the Commit History page opens a detailed view of the changes that are included in that commit.

​
Version Control Operations

Git version control provides the following operations for managing workspace configuration changes.

​
Commit and Push

The Commit and Push operation saves local configuration changes to the repository. The commit dialog displays the following information:
  • a list of changed files
  • line-level differences for each file
You can select which changes to include, and you must provide a commit message. If the remote branch contains newer commits, the Commit and Push operation is disabled until you pull the latest changes.

​
Pull

The Pull operation retrieves changes from the remote repository and updates the workspace configuration. The pull interface displays available commits, including details such as author, message, and number of changes. applies pulled changes using a rebase strategy. If the workspace contains uncommitted local changes, the Pull operation is disabled until those changes are committed or discarded.

​
Discard Changes

The Discard Changes operation removes selected local changes from the workspace. This action requires confirmation and permanently removes the selected changes.

​
Restore Changes from a Commit

You restore changes from a commit by selecting the commit on the Commit History page and restoring the files that are included in that commit. To restore changes from a commit:
  1. Open Activity > Commit History and select the commit that contains the changes you want to restore.
  2. Open the commit details view to review the files and differences.
  3. Restore the files from the commit.
When you restore changes:
  • The selected changes are saved and applied locally to the workspace.
  • The changes are not committed automatically. You need to use Commit and Push to save the changes to the repository.

​
Branch Behavior

Git version control uses a single branch per workspace. You select the branch during configuration, and it cannot be changed after initialization. Branch creation, switching, and deletion are not supported. The current branch is displayed as a read-only value.

​
Conflict Prevention

prevents operations that can result in conflicts:
  • Commit and Push is disabled if the remote branch contains newer commits.
  • Pull is disabled if the workspace contains uncommitted local changes.
These constraints ensure that changes are applied in a consistent order.

​
Workspace Encryption Keys

Each workspace uses a dedicated encryption key for version control. When connects to a repository, it can create a new key if no existing configuration is detected in the selected branch. If detects existing workspace settings in the repository, it prompts you to import the corresponding encryption key. You can also export encryption keys from a workspace for reuse in other environments. Exported keys should be protected with a password.