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 hi

Question

Options

• AEach developer commits their code to the main branch before each product release, conducts
• BEach group of developers copies the repository, commits their changes to their repository, and
• CEach developer creates a branch for their own work, commits their changes to their branch, and
• DEach group of developers creates a feature branch from the main branch for their work, commits

• A
  4% (1)
• B
  8% (2)
• C
  4% (1)
• D
  85% (22)

Explanation

Google's recommended SCM best practice for high software delivery rates is trunk-based development or short-lived feature branches merged frequently into the main branch. Option D best captures this: groups create short-lived feature branches, commit changes, and merge back to main frequently. This minimizes long-running divergence between branches, reduces merge conflicts, and keeps the codebase in a releasable state - all key drivers of higher software delivery performance as evidenced by the DORA (DevOps Research and Assessment) metrics. Option A (committing to main only before release) introduces integration chaos. Option B (forking the entire repository) is an open-source contribution pattern unsuitable for a single team. Option C (individual developer branches) is closer but lacks the coordinated group-level workflow and explicit 'frequent merge' discipline described in D.

No community discussion yet for this question.