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
  7% (1)
• B
  7% (1)
• C
  87% (13)

Explanation

Google's DORA research and DevOps best practices recommend that each developer work on their own short-lived feature branch, commit frequently, and merge back to the main branch via pull requests (code reviews). This aligns with trunk-based development principles, reduces merge conflicts, enables continuous integration, and drives higher software delivery performance. Option A (committing to main only before release) delays integration and increases risk. Option B (team-level forks) creates long-lived divergence and complex merge scenarios. Option D (group feature branches) introduces the same coordination overhead and merge complexity at the group level.

No community discussion yet for this question.