知识卡片
审查位置影响反馈
拉取请求把人工审查放在合并和发布候选构建之前,易于强制审查但拉长内循环。主干开发依赖足够快且可靠的自动测试,使小增量提交快速形成候选构建;仍可通过结对或后续流水线阶段审查。取舍是人工审查的位置和工程成熟度,不能把主干开发理解成不审查。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与分发基础设施代码 · 查看原书依据
The key trade-off between the PRs and TBD is feedback loops versus how manual code reviews are implemented. Figure 15-5 compares the two workflows. Figure 15-5. Comparing PR and TBD workflows The two workflows differ in where code review sits in relation to publishing a
参考来源
- 位置:《Infrastructure As Code》第15章《构建与分发基础设施代码》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch15.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“拉取请求把人工审查放在合并和发布候选构建之前,易于强制审查但拉长内循环”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:The key trade-off between the PRs and TBD is feedback loops versus how manual code reviews are implemented. Figure 15-5 compares the two workflows. Figure 15-5. Comparing PR and TBD workflows The two workflows differ in where code review sits in relation to publishing a