Suite Git Integration (dbt Cloud Model)
Problem
Suite has no Git collaboration workflow. Analytics teams expecting a dbt Cloud-style experience — connect a repo, work on branches, review changes, and promote to production — have no way to do any of this from the hosted application. Without branch isolation and review flows, multiple analysts editing the same project risk overwriting each other's work, and there is no safe path to promote dashboard changes through environments. This blocks any team that needs governed, multi-user collaboration on analytics content.
Context
- Users can connect repos, create/manage branches, and sync changes from Suite.
- Collaboration model supports review/approval and clear environment promotion.
- Operational controls (auth, audit trail, conflict handling) are documented and tested.
Possible Solutions
- A - Keep Git operations external and document a manual workflow: simplest, but weak for the hosted-product goal.
- B - Recommended: define a constrained hosted Git collaboration model: support repo connection, branch creation/sync, review/promotion handoffs, and failure states inside Cloud Suite.
- C - Build full dbt Cloud parity immediately: ambitious, but too broad for the initial Suite collaboration layer.
Plan
- Define end-to-end UX and backend workflow for repo connect/branch lifecycle.
- Implement auth/credential handling and repository permission boundaries.
- Add conflict resolution and status signaling in UI for sync/publish flows.
- Validate with pilot users against real collaboration scenarios.
- Publish runbook/docs for administrators and analysts adopting the model.
Implementation Progress
- GitHub issue: https://github.com/fivetran/dataface/issues/301
QA Exploration
- [ ] QA exploration completed (or N/A for non-UI tasks)
Review Feedback
- [ ] Review cleared