u/GrimFunko

I’m running into a pain point with Fabric’s Git integration and I can’t tell if I’m missing something obvious or if this is just how it works.

Scenario:

• Dev workspace linked to dev branch
• I create a feature branch + separate workspace (using the branch-out approach)
• Build out a new ingestion process:
  • Notebook
  • Lakehouse + supporting items
  • Pipeline (runs notebook, alerts, etc.)

So far, so good.

The problem comes when merging back. After merging the feature branch into dev and syncing the dev workspace…

The pipeline’s Run Notebook activity still points to:

• the feature workspace ID
• the feature notebook ID

So now the pipeline in dev is effectively wired to the wrong workspace/items.

Workarounds I can see:

• Parameterise reference IDs - workspace id is very doable, but notebook references are messy (Fabric API calls, web activities, etc.)
• Manually fix IDs post-merge - means another branch + PR just to fix references

My confusion is that Fabric seems to be pushing Git integration, workspace feature branching and UI-driven development, but in reality, these don’t seem to work well together when it comes to item references.

So:

• How are people handling this in practice?
• Is there a clean pattern I’m missing?
• Or is this just a gap in the current model?

Would really appreciate hearing what’s worked (or hasn’t) for others.