DevOps Setup

The Master Data platform is held in a single Azure DevOps repository. Bronze and SilverGold are developed against different branches, each pinned to the folder its Fabric workspace git-integrates from. 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-masterdata-core

Layer	Git Folder	Source Branch
Bronze	/Bronze	main
SilverGold	/SilverGold	AddMasterData

• The repo is cloned once locally into repos\bi-data-platform-masterdata-core\. Both top-level folders — Bronze/ and SilverGold/ — are visible in the same working tree.
• Which folder's contents are authoritative depends on the branch currently checked out. Bronze work is done from main (via workingBronze); SilverGold work is done from AddMasterData (via workingSilver).

Two local working branches let Bronze and SilverGold be developed and pushed independently. Each was created with --no-track off its source branch, so a push never accidentally targets main or AddMasterData directly.

Working Branch	Based On	Scope	Remote Push Target	PR Target
workingBronze	origin/main	Bronze changes only	origin/workingBronze	main
workingSilver	origin/AddMasterData	SilverGold changes only	origin/workingSilver	AddMasterData

• Independent pushes. git push origin workingBronze and git push origin workingSilver 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 SilverGold folders while on workingBronze, or Bronze folders while on workingSilver. Keeps PR diffs clean and prevents accidental cross-workspace commits.
• The process is stable; the target branches are configuration. The specific branches each layer syncs from today (main for Bronze, AddMasterData for SilverGold) may change over time. If they do, the workflow pattern does not change — push workingBronze / workingSilver and PR into whichever branch each layer currently syncs from. Always confirm the current PR target in the workspace's Git integration settings before raising a PR.