DevOps Setup

Two Fabric workspaces support the Reapit data platform. Both git-integrate with the same Azure DevOps repository via the workspace Git integration setting, each pinned to a specific folder and long-lived development branch. Locally, a single clone of the repo holds both folders side-by-side at the top level.

• Provider: Azure DevOps
• Organization / Project: savills-uk / Savills Applications
• Repository: bi-data-platform-reapit-core

Fabric Workspace	Git Folder	Branch
Reapit Bronze	/Bronze	ReapitBronzeInitialDev
Reapit SilverGold	/SilverGold	InitialSilverDevelopment

• The repo is cloned once locally into repos\bi-data-platform-reapit-core\. Both top-level folders — Bronze/ and SilverGold/ — are visible in the same working tree.
• Which folder's contents are "current" depends on the branch currently checked out. Bronze contents materialise when on ReapitBronzeInitialDev (or a branch off it); SilverGold contents materialise when on InitialSilverDevelopment.

Two local working branches let Bronze and SilverGold be developed and pushed independently. Each pushes to its own remote and PRs into the long-lived dev branch that the matching Fabric workspace syncs from.

Working Branch	Scope	Remote Push Target	PR Target
working-bronze	Bronze changes only	origin/working-bronze	ReapitBronzeInitialDev
working-silver	SilverGold changes only	origin/working-silver	InitialSilverDevelopment

• Independent pushes. git push origin working-bronze and git push origin working-silver are completely separate operations — neither affects the other.
• Fabric refresh on merge. When a PR is merged, the matching Fabric workspace picks up the change on its next Git sync. Bronze merges refresh the Bronze workspace; Silver merges refresh SilverGold.
• Single-domain rule. Do not touch Bronze folders while on working-silver, or SilverGold folders while on working-bronze. Keeps PR diffs clean and prevents accidental cross-workspace commits.
• main is not in this loop. Integration from the dev branches into main happens separately — working-branch PRs never target main directly.
• The process is stable; the target branches are configuration. The specific branches the Fabric workspaces sync from today (ReapitBronzeInitialDev, InitialSilverDevelopment) may change over time. If they do, the workflow pattern does not change — push working-bronze / working-silver and PR into whichever branch each workspace currently syncs from. Always confirm the current PR target in the workspace's Git integration settings before raising a PR.