Git Sync
Git Sync exports selected AutoBP assets to a local repository for review, version control, and collaboration.
Setup
Git Sync is configured per organization. The first milestone focuses on a DB-primary export flow: AutoBP remains the source of truth, and selected assets are serialized to a local Git working tree.
Open Git Sync from the Dashboard or Settings.
Configure the local repository path.
Verify repository access and branch state.
Choose export format and whether to include environments or data assets.
Preview changes before committing.
Preview And Export
Preview is the important safety step. It shows changed bundles, generated file content, and warnings before any commit is created.
Practical Tips
- Review BP Groups, Environments, and Test Suites separately.
- Do not export secrets; environment exports should contain safe configuration and placeholders only.
- Commit with a message that explains the workflow or suite change, not just Sync updates.
What Gets Synced
Git Sync focuses on AutoBP definition assets such as BP groups, implementations, suites, cases, steps, hooks, and safe environment configuration. Test data and BP data are optional because some teams treat them as sensitive or tenant-specific.
Choose whether to include environments.
Choose whether to include data assets.
Review the changed bundle list.
Exclude bundles that should not be part of the current commit.
Export and push using your normal repository process.
Branch And Repository Hygiene
Git Sync works best when the local repository is clean before export. Existing uncommitted changes can hide generated changes or make reviews confusing.
Practical Tips
- Use one branch per business change or release package.
- Preview before export, then inspect the Git diff after export.
- Keep commit messages short but specific.