标题： 选择正确的 Git 工作流：基于主干与基于分支方法的比较分析 显示英文标题

标题： Choosing the Right Git Workflow: A Comparative Analysis of Trunk-based vs. Branch-based Approaches

摘要： Git如今已成为最广泛使用的版本控制系统之一。 在其众多特点中，其易于且快速创建分支的能力尤为突出，使团队能够自定义其工作流程。 在这一背景下，各种使用Git的协作开发工作流程相继出现，并在软件工程师中受到欢迎。 我们可以将这些工作流程分为两大类：基于分支的工作流程和基于主干的工作流程。 基于分支的工作流程通常定义一组具有明确目标的远程分支，例如功能分支、一个用于功能集成的分支以及一个主分支。 其目标是随着代码的成熟，将最孤立的分支中的更改迁移到所有人员共享的主分支中。 在这一类别中，GitFlow是最受欢迎的示例。 相比之下，基于主干的工作流程只有一个远程分支，开发人员直接在此分支上集成他们的更改。 在这个选项范围内，选择一种既能最大化团队生产力又能促进软件质量的工作流程成为一个非 trivial 的任务。 尽管在论坛、社交网络和博客上进行了讨论，但很少有科学文章探讨过这个主题。 在本研究中，我们提供了关于巴西开发者如何使用Git工作流程以及哪些因素促进或阻碍每种模型使用的证据。 为此，我们对软件开发人员进行了半结构化访谈和调查。 我们的结果表明，基于主干的开发更适合经验丰富的小型团队的快节奏项目，而基于分支的开发更适合经验较少的大团队，尽管这会带来管理上的挑战。 显示英文摘要

摘要： Git has become one of the most widely used version control systems today. Among its distinguishing features, its ability to easily and quickly create branches stands out, allowing teams to customize their workflows. In this context, various formats of collaborative development workflows using Git have emerged and gained popularity among software engineers. We can categorize such workflows into two main types: branch-based workflows and trunk-based workflows. Branch-based workflows typically define a set of remote branches with well-defined objectives, such as feature branches, a branch for feature integration, and a main branch. The goal is to migrate changes from the most isolated branch to the main one shared by all as the code matures. In this category, GitFlow stands out as the most popular example. In contrast, trunk-based workflows have a single remote branch where developers integrate their changes directly. In this range of options, choosing a workflow that maximizes team productivity while promoting software quality becomes a non-trivial task. Despite discussions on forums, social networks, and blogs, few scientific articles have explored this topic. In this work, we provide evidence on how Brazilian developers work with Git workflows and what factors favor or hinder the use of each model. To this end, we conducted semi-structured interviews and a survey with software developers. Our results indicate that trunk-based development favors fast-paced projects with experienced and smaller teams, while branch-based development suits less experienced and larger teams better, despite posing management challenges.