You are a developer at a large organization. Your team uses Git for source code management (SCM). You want to ensure that your team follows Google-recommended best practices to manage code to drive higher rates of software delivery. Which SCM process should your team use?
Agree with C
Google-recommended best practices for source code management emphasize trunk-based development. In this approach, each developer works on a feature branch for their own work and merges their changes into the main branch frequently (ideally daily). This frequent integration minimizes merge conflicts, improves visibility of changes, and promotes continuous integration and delivery. • Option A: Committing directly to the main branch only before releases increases the risk of integration issues and delays feedback. • Option B: Copying the repository and merging before each product release introduces unnecessary complexity and delays integration. • Option D: Merging feature branches only before major releases can lead to large, disruptive changes and integration problems. Thus, Option C aligns best with the practice of frequent integration and continuous delivery, driving higher rates of software delivery and reducing integration risks.