How do Collections and Git sync work?
TL;DR: Collections are folders that organize playbooks in your workspace. Optionally connect a collection to a Git repository for version control, team collaboration, and review workflows. Git sync tracks changes between Ballet and the remote repo — drift means the two versions differ.
Who this is for
Builders organizing playbooks and teams using Git-based review workflows.
What is a collection?
A collection is a folder containing related playbooks. Use collections to group automations by team, project, or domain — for example, "Support Automations" or "Engineering Integrations."
How do I browse collections?
Open Collections from the sidebar. You'll see your workspace folders and the playbooks inside each one.
What is Git sync?
Git sync connects a collection to a Git repository. Playbook definitions sync between Ballet and the repo, enabling:
- Version history — track changes over time in Git.
- Code review — teammates review playbook changes via pull requests.
- Team collaboration — multiple builders work on the same collection.
What is drift?
Drift occurs when the Ballet version and the Git remote version differ — someone edited in Ballet without pushing, or pushed to Git without pulling into Ballet. Resolve drift by syncing in the direction you want to be authoritative.
Should I use Git sync?
Use Git sync when:
- Your engineering team wants reviewable, version-controlled automations.
- Multiple builders collaborate on the same playbooks.
- You need audit trails for production workflow changes.
Skip Git sync for quick experiments and personal drafts.