Your security team tracks IAM access and you need a version control setup that integrates with that process while supporting fast releases and frequent merges to reduce conflicts. What should you do?

Creating a Cloud Source Repositories (CSR) repo directly integrates with Google Cloud's IAM system, allowing your security team to track access effectively. Adopting trunk-based development (TBD) supports fast releases and frequent, small merges, which inherently reduces merge conflicts compared to long-lived branches. TBD aligns with continuous integration/continuous delivery (CI/CD) practices, crucial for rapid development. Using feature-branch development, whether with CSR or GitHub, involves longer-lived branches and less frequent merges, increasing the likelihood of merge conflicts and slowing down release cycles. While GitHub repos can be mirrored to CSR, this adds an unnecessary layer of complexity and potential synchronization issues if the primary goal is IAM integration within Google Cloud. Direct use of CSR is more straightforward for Google Cloud-centric security and development workflows.