In GitHub, why is it recommended to deploy from your feature branch before merging into the main branch?

Question

Options

• ATo directly deploy changes from the main branch without any intermediate testing
• BTo speed up the process of merging changes into the main branch
• CTo avoid the need for testing changes in production
• DTo ensure the changes are verified and validated in a production environment

• A
  6% (1)
• B
  6% (1)
• D
  88% (15)

Explanation

Deploying from a feature branch to a production (or production-like) environment before merging into main is a best practice because it validates that the changes work correctly under real-world conditions. If issues are discovered post-merge on main, rolling back is more complex and affects all users. This practice, sometimes called 'deploy then merge,' ensures the feature is verified in production before it becomes part of the canonical codebase.

No community discussion yet for this question.