DevOps Setup

Two Fabric workspaces support the EU Finance data platform. Both git-integrate with the same Azure DevOps repository via the workspace Git integration setting, each pinned to a specific folder. Unlike Reapit, both workspaces sync directly from main. 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-eufinance-core

Fabric Workspace	Git Folder	Branch
EU Finance Bronze	/Bronze	main
EU Finance SilverGold	/SilverGold	main

• The repo is cloned once locally into repos\bi-data-platform-eufinance-core\. Both top-level folders — Bronze/ and SilverGold/ — are visible in the same working tree.
• Because both workspaces sync from main, both folders' contents are current whenever the checkout is on main or a branch freshly cut from it.

Two local working branches let Bronze and SilverGold be developed independently. Both are cut from main and exist locally only — they are pushed to origin only at the point a PR is raised. PRs target main, which both Fabric workspaces sync from.

Working Branch	Scope	Remote Push Target	PR Target
WorkingBronze	Bronze changes only	origin/WorkingBronze (on PR only)	main
WorkingSilver	SilverGold changes only	origin/WorkingSilver (on PR only)	main

• Local until PR time. Neither working branch lives on origin during development. Push only when raising a PR, and each push is a completely separate operation — neither affects the other.
• Fabric refresh on merge. When a PR is merged to main, both workspaces see the commit on their next Git sync, but only the workspace whose folder changed picks up actual content changes. Bronze merges refresh the Bronze workspace; SilverGold merges refresh SilverGold.
• Single-domain rule. Do not touch Bronze folders while on WorkingSilver, or SilverGold folders while on WorkingBronze. Keeps PR diffs clean and prevents accidental cross-workspace commits.
• Rebase from main regularly. Because both branches PR into main, keep each working branch up to date with main before starting new work to avoid merge conflicts at PR time.
• The process is stable; the target branches are configuration. If the Fabric workspaces are later repointed at dedicated dev branches (as Reapit uses), the workflow pattern does not change — push WorkingBronze / WorkingSilver 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.