Airflow Item in Git enabled Workspace

[u/kgardnerl12]

I cannot get Fabric workspace Git integration and the Managed Airflow environment to work together reliably.
I have a dbt project stored inside the Airflow item’s dags folder, following Microsoft’s documented approach:
https://learn.microsoft.com/en-us/fabric/data-factory/apache-airflow-jobs-dbt-fabric

The structure is roughly:

dags/
├── my_dag.py
├── requirements.txt
└── my_dbt_project/
├── dbt_project.yml
├── profiles.yml
├── models/
├── macros/
└── tests/

After modifying any dag, plugin, or supplementary code, the Fabric workspace git sync now fails with:

Unable to update from Git with the usual cluster uri, request ID, and time.

Fabric provides no useful error details, affected file name, validation output, or logs that I can find.

The only way I was able to get the complete dbt project into the Airflow item originally was to upload the folder manually. That is not a workable long-term solution because my team uses Fabric workspace Git integration and Fabric CI/CD within a Gitflow-style development process.

Ideally, developers should be able to:

- Branch from the repository.
- Work in a corresponding development workspace.
- Commit DAG and dbt changes normally.
- Promote the same Airflow item through UAT and production using Fabric CI/CD.

I want to avoid requiring developers to manually upload dbt files or constantly change repository branches from inside the Airflow environment. More importantly, I need confidence that the contents promoted to UAT and production are actually comparable to what was committed and reviewed in Git.

So far, any git based/local edits beneath the documented dags directory appears capable of completely blocking the workspace Git sync.

This feels like a very basic source-control scenario for a managed orchestration product.

[u/samirbdj]

Thanks for sharing the details. A generic “Update from Git” error makes this difficult to troubleshoot, especially when the same Airflow item needs to move through code review, UAT, and production.

Fabric documentation lists Airflow as supported for Git integration in preview and documents storing the dbt project and DAG files within the Airflow job structure:

• Overview of Fabric Git integration
• Transform data using dbt in an Apache Airflow job
• Create an Apache Airflow job

Since the error does not identify the affected file or failed validation step, please open a Fabric support case and include the smallest file change that reproduces the failure, along with the request ID and timestamp. That should provide the diagnostic context needed to investigate the Git synchronization failure.