Enable javascript in your browser for better experience. Need to know to enable it? Go here.
Published : Sep 27, 2023
NOT ON THE CURRENT EDITION
This blip is not on the current edition of the Radar. If it was on one of the last few editions, it is likely that it is still relevant. If the blip is older, it might no longer be relevant and our assessment might be different today. Unfortunately, we simply don't have the bandwidth to continuously review blips from previous editions of the Radar. Understand more
Sep 2023
Assess ?

我们一直是短暂开发分支的倡导者,这些分支经常合并到主代码分支中,主代码分支始终准备好进行部署。这种主干开发的实践与持续集成密切相关,并且在条件允许的情况下,可以实现最快的反馈循环和最高效的开发流程。然而,并不是每个人都喜欢这种方法,我们经常根据客户的实践来调整我们的风格。有时,这包括长期存在的特性分支和拉取请求必须被手动审查和批准,然后才能将它们合并到主分支中。在这些情况下,我们使用新的 GitHub 合并队列功能 GitHub 合并队列功能。它允许我们自动排队接收的拉取请求,并将它们合并到特殊分支中,按接收顺序进行排序。然后,我们可以选择自动执行我们自己的“合并检查”,以防止不兼容的提交。这本质上是模拟主干开发(即使 PR 尚未合并到主代码分支中),允许开发人员在上下文中测试其功能,而无需等待批准拉取请求。使用 GitHub 合并队列,即使你不能直接提交到主干,也可以获得主干开发的好处。

Download the PDF

 

 

 

English | Português 

Sign up for the Technology Radar newsletter

 

 

Subscribe now

Visit our archive to read previous volumes