Git integration and feature branching strategy across Dev Test Prod workspaces in Microsoft Fabric

I think Dev on dev, with Deployment Pipelines to Test/Prod, is simpler than separate environment branches. Use feature workspaces with sample lakehouse data. Enable notebook Lakehouse Auto-Binding in Git. Variable Library's active value set must be selected per workspace. Git doesn't store that choice.

Cross-workspace references won't auto-bind. External shortcuts retain their targets, and Direct Lake SQL endpoint URLs/database IDs in TMDL need remapping. SQL endpoint objects need separate scripts or preview CI/CD. Resolve notebook, pipeline and TMDL conflicts in PRs. Merge into dev, sync Dev, validate in Test, then deploy to Prod. Delete feature workspaces after dependency checks. Git moves metadata, not lakehouse data.