@MrDecisive 

Based on your requirements, I would recommend adopting a dedicated repository per team. While it may require some upfront effort in terms of setup and governance, it will significantly streamline development and deployment processes in the long run. Decoupling teams and codebases improves autonomy, reduces dependencies, and simplifies maintenance.

A single repository is more suitable in a Data Fabric architecture where multiple teams contribute shared code, definitions, or assets that need to be centrally managed and consumed by downstream systems. In such scenarios, a fork-based workflow may be more practical than relying solely on pull requests.

Overall, unless you are implementing a Data Fabric model or building a quick proof of concept, a repository-per-team approach aligns better with Data Mesh principles and is generally the preferred option.