Enabling Git Integration in Swimlane Turbine

swimlane turbine offers git integration, allowing you to sync the content in your turbine library with a remote github/gitlab repository this ensures proper version control, collaboration, and easy recovery of your turbine content why git integration? change management audit trails and accountability git provides a clear history of all changes, including who made them and when this is critical for organizations needing to track modifications and understand events leading to the current state of their system it helps enforce accountability, especially in collaborative environments integrity and security immutable history and backup or recovery once changes are committed to git, they become part of a permanent history that cannot be altered without evidence, protecting the integrity of your data git repositories can also be backed up, ensuring that you can recover data in case of any loss or mishap regulatory compliance documentation and evidence git’s logs and commit messages serve as evidence during audits and compliance assessments it provides documentation that is useful for demonstrating an organization’s adherence to change management and version control best practices incident response and forensics rollback capabilities git makes it easy to revert changes, allowing for quick restoration in case of harmful or accidental modifications this minimizes the risk of disruptions from unauthorized or erroneous changes and helps in forensic investigations to understand incidents and recover from them setting up the git repository to setup git repository in swimlane turbine from the admin panel access git integration from the admin panel , navigate to settings > account and click on the git integration tab enable github remote repository toggle the enable remote git repository option to turn on git integration this allows you to synchronize your turbine library with a remote github repository synchronization settings turbine automatically syncs changes this option will ensure that changes between the turbine library and the remote repository are automatically synced manual sync select this option if you prefer to manually push and pull changes between the turbine library and the remote repository configuring remote repository repository url enter the url of your remote github or gitlab repository authentication type ssh key enables secure and automated access recommended access token use personal access token (github) or project access token (gitlab) when ssh key is selected click generate ssh key to generate a key the public key will be shown click copy to add it to your git repository's deploy key settings once the key is generated, it is automatically saved the save button will remain disabled however, if you delete the key, you must click save to confirm the change when access token is selected if you prefer to authenticate using a personal or project access token, select the access token option under authentication type token source choose between github personal access token gitlab project access token personal access token / project access token paste the generated token into the input field if you are using a github personal access token, ensure that it includes the following permissions contents (read and write) and metadata (read only) click test connection to verify access to the git repository you must click save after entering or deleting an access token now your swimlane turbine instance is connected to the remote git repository depending on your sync mode, changes will be synced automatically or on demand quick reference git integration settings repository url format ssh mailto\ git\@github com \ org/repo git https https //github com/org/repo git authentication options ssh key generated in swimlane ui auto saved upon generation must be saved manually if deleted access token user provided save required after entering or deleting github pat must include contents read + write metadata read only sync modes automatic or manual (controlled via git integration settings) conflict resolution per application (package level) — user can resolve each item individually important considerations for using external git repositories these rules ensure compatibility and reliability when using external git repositories with turbine ignoring them may result in sync errors or unsupported behaviors purpose external git repositories are intended for backup , versioning , and cross environment content sharing do not manually modify the files in the git repository all turbine content should be edited within the turbine platform and then pushed to the remote repository deployment support external repositories are supported in both turbine cloud and on premise environments for air gapped deployments , outbound network access must be configured to allow connectivity to git services (e g , github, gitlab) repository size limit the total size of the external git repository must not exceed 100mb branching behavior branching and cherry picking are currently not supported all commits are merged into the main branch