AZ-400: Designing and Implementing Microsoft DevOps Solutions Practice Exam

In the Git branching model, the recommended practice for developing a new feature is to use short-lived branches. This approach encourages a quick and efficient workflow, allowing developers to focus on implementing features without prolonged isolation from the main codebase. Typically, a short-lived branch is created specifically for a single feature and is merged back into the main branch (often referred to as 'develop' or 'main') once development is complete and the feature is stable.

Short-lived branches help in minimizing integration issues and ensuring that the main branch remains up to date. Additionally, this practice allows for easier collaboration among team members, as it encourages frequent merges and reviews. By keeping branches short-lived, teams can effectively leverage Continuous Integration (CI) practices, enabling automated processes for testing and deploying code changes more swiftly.

In contrast, long-lived branches are usually less optimal for feature development, as they can lead to complexities with merging and increase the risk of code drift. Permanent branches do not align with the flexible and adaptive nature of modern development practices, while temporary might imply a less structured approach that could lead to mismanaged workflows. The succinct nature of short-lived branches makes them a best practice in the Git branching model for feature development.