On this page
Articles in this section
The SnapLogic Git Integration currently supports GitHub.com or, with a subscription, GitHub Enterprise Server (GHES). The Git Integration allows you to track, update, and version SnapLogic Projects, files, Pipelines, Tasks, and Accounts from the SnapLogic user interface. SnapLogic APIs also support Git checkout, pull, and check status operations.
After a Git Integration is enabled for a SnapLogic Org and a user has authorized and authenticated their account, they can add Project Assets to a repository. Users having access to the Project can collaborate. If you use different Orgs for development, testing, and production, the Git Integration can track the same Project Assets across all of the Orgs, supporting Continuous Integration and Continuous Development (CI/CD). The Git Integration supports Gitflow workflow and Trunk-based development, but we recommend trunk-based development.
The Project can have a maximum of 200 files. If checking out a Project with more than 200 files, SnapLogic throws an error.
Snap Pack and Snaplex Assets cannot be tracked in GitHub.
To enable one of the Git Integrations:
A repository for each Project must exist or be created in the appropriate GitHub organization or in GHES.
GitHub requirements include the following:
For organizational repositories, a GitHub organization administrator must install a SnapLogic App in GitHub.
For personal repositories, the owner must install a SnapLogic App in GitHub.
GHES requirements include the following:
A GHES administrator must create a SnapLogic App in GHES
An IT administrator must set up secure network connections.
For both GitHub and GHES, user accounts must have read and write access to the GitHub repositories and SnapLogic Projects. Individual users must authorize SnapLogic to interact with GitHub or GHES
The following pages provide procedures for configuring the Git Integration for: