Syntasa’s GitSync feature allows users to push the application’s development workflow directly into a Git repository (GitHub, GitLab, or Bitbucket). This streamlines version control, promotes team collaboration, and improves governance by integrating your workflow management with your source control system.
Once the Git repository has been configured in the Admin Center → Infrastructure, users will be able to use the Git Sync feature available on the development workflow screen. To learn more about configuring a GIT repository, please visit the article Configuring SCM for the GitSync.
Git Sync from Development Workflow
On the Development Workflow screen of any application, a Git Sync button is available in the top-right corner. Clicking this button opens a pop-up window that allows users to prepare and initiate a Git push.
The Git Sync Pop-Up shows the following options
- Add Notes (Optional): Enable the toggle to include development workflow notes along with the commit. This can be useful for providing more context or internal comments about the workflow being pushed.
- Commit Message (Required): This is a mandatory field and acts as the commit message in the Git repository. It helps describe the purpose or nature of the changes being pushed.
- Git Push Button: Once all fields are completed, clicking the Git Push button initiates a backend job named Git Sync.
How does Git Sync work?
When Git Push is triggered, Syntasa runs a job titled Git Sync. This job performs two key processes:
-
App Export
This process gathers the code and configurations from the development workflow and generates the files that will be committed to Git. It functions similarly to the Export feature used for downloading the application as a ZIP file — except in this case:
- Files are not zipped.
- Files are prepared and structured to be ready for a direct Git commit.
-
Git Commit
Once files are prepared, this process pushes the generated files to the Git repository and branch specified under the Infrastructure settings. The push includes:
- The files created during App Export
- The user-provided commit message
- Notes (if toggle enabled)
About Git Sync Job
The Git Sync job behaves like a Deploy job:
- It does not require a runtime or execution date range.
- It does not appear under the standard Activity → Job or Activity → Execution screens.
- It can be tracked only from the Operations screen of the Workflow.
This ensures that GitSync activities are kept cleanly separated from data pipeline execution jobs and runtime processes.
Pushing Workflow to Git From the Snapshot Screen
GitSync is not limited to the Development Workflow screen. It is also available on the Snapshot Screen. When taking a snapshot of the development workflow, you have the additional option to push the development workflow to the Git repository. You can follow the steps below to navigate to the Snapshot screen:
- Navigate to the development workflow.
-
Click the triple-dot icon (
) next to the 'Deploy' button (
) and select 'Snapshot' from the options.
Pushing Workflow to Git From the Deploy Screen
During deployment of the development workflow to production, you will see the option to push the development workflow to Git. This helps preserve the current state of the development workflow in Git alongside promoting it to production.