Warehouse, git integration and dbt

If the Fabric/Git integration does not support .gitignore, I'd expect that no, there is no way to prevent Fabric from tracking certain changes in the Warehouse. The integration looks at the warehouse as one singular object, so picking and choosing what is/is not tracked or deployed hasn't been a feature.

As for workarounds, I can think of two directions you could go depending on where you want to manage your deployment process:

1. Somewhere between your dev's branches and your trunk you'd have to create an approach that either cherry picks what you want to merge to trunk, or creates an intermediate branch that can then be modified before changes are merged into trunk.
2. If you're looking to source control dbt SQL files within your warehouse, you can use a Schema Compare in visual studio to compare between two warehouses and create deployment scripts. You'd then keep your dev/feature branches separate from your trunk branch, and your commit to the trunk branch would be from your Prod workspace rather than a merge from a feature branch.
   1. If you want to see what the schema compare looks like, I made a video on my Youtube channel on this approach recently. You can find it here: https://youtu.be/OWF6YlAAY54?si=AhLY9p9QfLx0puQe

I've heard there might be changes coming to the git integration and deployment process in the future, but no idea when.

Once you've found a suitable answer, be sure to select your answer so other community members can learn from it.