WEBVTT
NOTE Generated by scripts/generate-bilingual-video-tracks.mjs from codex-HwbSWVg5Ln4.en.vtt and codex-HwbSWVg5Ln4.zh-Hans.vtt.

1
00:00:00.000 --> 00:00:04.400
Code review, but one take, two. Comment
代码审查，但要一次通过，两次通过。 评论

2
00:00:02.600 --> 00:00:06.240
mark. I agree.
标记。 我同意。

3
00:00:04.400 --> 00:00:09.160
You're getting
你现在听到的是：

4
00:00:06.240 --> 00:00:12.040
Hey everyone, I'm Romain. And I'm Maya.
大家好，我是罗曼。 我是玛雅。

5
00:00:09.160 --> 00:00:14.400
Codex needs to do two things really well
Codex 要想

6
00:00:12.040 --> 00:00:16.040
to be an effective coding teammate.
成为一名高效的编码团队成员，需要做好两件事。

7
00:00:14.400 --> 00:00:19.040
First, it needs to work with all your
首先，它需要与你所有的

8
00:00:16.040 --> 00:00:21.360
tools. And second, it also needs to plug
工具兼容。 其次，它还需要融入

9
00:00:19.040 --> 00:00:22.880
into all of your team workflows.
到你团队的所有工作流程中。

10
00:00:21.360 --> 00:00:25.000
Code review is one of the most important
代码审查是

11
00:00:22.880 --> 00:00:26.960
workflows for any engineering team, and
任何工程团队最重要的工作流程之一，

12
00:00:25.000 --> 00:00:29.960
we want to help there as well.
我们也希望在这方面提供帮助。

13
00:00:26.960 --> 00:00:32.040
With GPT-5 and now GPT-5 Codex, we
我们使用 GPT-5 和现在的 GPT-5 Codex

14
00:00:29.960 --> 00:00:34.720
trained these models specifically to
训练这些模型，专门用于

15
00:00:32.040 --> 00:00:37.000
find bugs and investigate some issues.
查找错误和调查一些问题。

16
00:00:34.720 --> 00:00:39.080
Maya, why don't you tell us more? Sure.
玛雅，你为什么不多跟我们说说呢？ 当然。

17
00:00:37.000 --> 00:00:41.200
I work on alignment team within OpenAI
我在 OpenAI 研究部门的对齐团队工作

18
00:00:39.080 --> 00:00:42.920
research, and code review is a very
，代码审查是

19
00:00:41.200 --> 00:00:45.280
important research project for us. As
我们非常重要的研究项目。 随着

20
00:00:42.920 --> 00:00:47.080
the AI capabilities grow and we have
人工智能能力的提升和功能

21
00:00:45.280 --> 00:00:49.160
more and more powerful coding agents, we
越来越强大的编码代理的出现，我们

22
00:00:47.080 --> 00:00:51.680
are producing a lot of code, and human
产生了大量的代码，而人工

23
00:00:49.160 --> 00:00:53.880
verification is becoming the bottleneck.
验证正成为瓶颈。

24
00:00:51.680 --> 00:00:56.280
So, we need to make sure that while also
因此，我们需要确保在

25
00:00:53.880 --> 00:00:58.080
training powerful models to help humans
训练强大的模型来帮助人类

26
00:00:56.280 --> 00:01:00.360
in verification, and that our
进行验证的同时，我们的

27
00:00:58.080 --> 00:01:03.080
verification abilities are scaling as
验证能力能够像

28
00:01:00.360 --> 00:01:05.680
fast as AI capabilities. That's why we
人工智能的能力一样快速扩展。 这就是我们

29
00:01:03.080 --> 00:01:07.560
trained code review models, and we could
训练代码审查模型的原因，我们本来可以像

30
00:01:05.680 --> 00:01:10.520
have done it just like other research
其他内部研究一样进行这项工作

31
00:01:07.560 --> 00:01:13.280
exercise internally, but it's actually
，但实际上

32
00:01:10.520 --> 00:01:15.680
way more useful to have it interact with
让它与

33
00:01:13.280 --> 00:01:17.400
our OpenAI code base and also release it
我们的 OpenAI 代码库交互并向

34
00:01:15.680 --> 00:01:19.000
externally. Well, I'm very much aligned
外部发布更有用。 嗯，我非常

35
00:01:17.400 --> 00:01:20.600
with our philosophy at OpenAI of like
认同 OpenAI 的理念，即

36
00:01:19.000 --> 00:01:21.960
iterative deployment and making sure the
迭代部署，并确保

37
00:01:20.600 --> 00:01:24.440
technology under its contact with
技术在

38
00:01:21.960 --> 00:01:26.800
reality. So, I'd love to enable code
实际应用中不断进步。 所以，我非常希望启用代码

39
00:01:24.440 --> 00:01:29.240
review. Can you show us how to do it?
审查功能。 你能教教我们怎么做吗？

40
00:01:26.800 --> 00:01:31.880
Absolutely. So, the first thing you will
绝对地。 所以，你首先

41
00:01:29.240 --> 00:01:34.280
have to do is to go in your Codex web
要做的是进入 Codex 的网页

42
00:01:31.880 --> 00:01:36.000
setting and just enable it. So, that's
设置，然后启用它。 就这么简单

43
00:01:34.280 --> 00:01:38.240
all it takes. And now, going forward to
。 现在，需要

44
00:01:36.000 --> 00:01:39.920
understand like any PR submitted to that
明确的是，提交到该仓库的任何 PR 都

45
00:01:38.240 --> 00:01:43.520
repo will be automatically reviewed by
将由 Codex 自动审核

46
00:01:39.920 --> 00:01:46.480
Codex. Exactly. So, for example, here I
。 确切地。 例如，我在这里

47
00:01:43.520 --> 00:01:48.560
quickly coded up some simple extension.
快速编写了一些简单的扩展程序。

48
00:01:46.480 --> 00:01:50.640
I created a pull request, and it's
我创建了一个拉取请求，它已被

49
00:01:48.560 --> 00:01:52.640
marked as ready for review. The code
标记为可供审核。 代码

50
00:01:50.640 --> 00:01:54.040
review agents will pick it up and start
审查员会接收并开始

51
00:01:52.640 --> 00:01:55.440
reviewing it. And in the meantime,
审查它。 与此同时，

52
00:01:54.040 --> 00:01:57.200
there's a little bit of a an emoji with

53
00:01:55.440 --> 00:02:00.040
the eyes over here. Exactly.
这里还有一个眼睛的表情符号。 确切地。

54
00:01:57.200 --> 00:02:02.240
>> Um why don't you show us one where Codex
嗯，为什么不给我们展示一个Codex

55
00:02:00.040 --> 00:02:04.080
has already completed the review? So,
已经完成审查的例子呢？ 再来

56
00:02:02.240 --> 00:02:05.960
here's another one. It looks a bit
一个。 看起来有点不

57
00:02:04.080 --> 00:02:08.119
different because here I triggered the
一样，因为这里我

58
00:02:05.960 --> 00:02:10.160
review already when the PR was in a
在 PR 还是草稿阶段的时候就已经触发了审核

59
00:02:08.119 --> 00:02:12.400
draft stage, and I didn't yet want it
，我当时还不想让

60
00:02:10.160 --> 00:02:14.560
real humans to look at it. So, that's an
真人查看它。 所以，这是一种很

61
00:02:12.400 --> 00:02:16.720
interesting technique. So, you manually
有意思的技术。 所以，您手动

62
00:02:14.560 --> 00:02:18.120
add Codex with the message, and it
将 Codex 添加到消息中，

63
00:02:16.720 --> 00:02:19.840
sounds like in this case, you also
听起来您在这种情况下也

64
00:02:18.120 --> 00:02:23.000
wanted to have specific instructions,
希望有具体的说明，

65
00:02:19.840 --> 00:02:25.400
right? Yeah, so you can always comment
对吗？ 是的，您随时可以

66
00:02:23.000 --> 00:02:27.040
at Codex review this PR, and you can add
在 Codex 上评论此 PR，并添加

67
00:02:25.400 --> 00:02:29.120
some extra information. For example,
一些额外信息。 例如，

68
00:02:27.040 --> 00:02:31.200
something that would help the agent
可以帮助代理人

69
00:02:29.120 --> 00:02:33.560
understand the PR, or you can instruct
理解公关稿，或者您可以指示

70
00:02:31.200 --> 00:02:35.080
it to focus on some specific area. Here,
它关注某些特定领域。 这就是

71
00:02:33.560 --> 00:02:36.440
what what I love about Codex code
我喜欢 Codex 代码

72
00:02:35.080 --> 00:02:38.120
review, and I want people to understand
审查的原因，我想让大家明白，

73
00:02:36.440 --> 00:02:40.400
like it's not just static analysis,
它不仅仅是静态分析，

74
00:02:38.120 --> 00:02:42.360
right? Like the model has access to
对吧？ 就像模型可以使用

75
00:02:40.400 --> 00:02:44.800
tools. It's able to check its own work,
工具一样。 它能够检查自身的工作，

76
00:02:42.360 --> 00:02:46.520
to run tests and commands. Can you show
运行测试和命令。 你能给

77
00:02:44.800 --> 00:02:49.640
us what happened behind the scene for
我们展示一下这次公关活动幕后发生了什么吗

78
00:02:46.520 --> 00:02:52.960
this PR? Yeah, so one important thing to
？ 是的，所以需要

79
00:02:49.640 --> 00:02:54.360
note is the model doesn't only look at
注意的一点是，该模型不仅仅关注

80
00:02:52.960 --> 00:02:56.520
the diff. It has access to the whole
差异。 它拥有对整个

81
00:02:54.360 --> 00:02:58.960
repository. It can track down
存储库的访问权限。 它可以追踪

82
00:02:56.520 --> 00:03:01.280
dependencies. It could try to understand
依赖关系。 它可以尝试

83
00:02:58.960 --> 00:03:03.280
it in a broader code base, which is very
在更广泛的代码库中理解它，这

84
00:03:01.280 --> 00:03:05.040
important when you're working on a very
在你处理非常

85
00:03:03.280 --> 00:03:07.040
complex code base, where you're not the
复杂的代码库时非常重要，因为你不是

86
00:03:05.040 --> 00:03:09.240
only contributor and you don't
唯一的贡献者，而且你并不完全

87
00:03:07.040 --> 00:03:10.320
understand it in its entirety.
了解它。

88
00:03:09.240 --> 00:03:12.320
>> And here, it sounds like you can also
听起来，在这里你也可以

89
00:03:10.320 --> 00:03:14.920
review all of the logs that led to that
查看导致该次审查的所有日志

90
00:03:12.320 --> 00:03:18.000
particular review, right? Yeah, so here
，对吗？ 是的，所以

91
00:03:14.920 --> 00:03:21.400
the model was not only browsing through
这个模型不仅浏览了

92
00:03:18.000 --> 00:03:23.360
the code base, but it actually decided
代码库，而且还决定

93
00:03:21.400 --> 00:03:25.480
to form some hypotheses and write some
提出一些假设，编写一些

94
00:03:23.360 --> 00:03:28.160
Python code to test the hypothesis and
Python 代码来测试这些假设，

95
00:03:25.480 --> 00:03:30.720
check whether it's actually correct and
检查它们是否真的正确，并

96
00:03:28.160 --> 00:03:32.840
show it on a couple of examples. That's
在几个例子中进行展示。

97
00:03:30.720 --> 00:03:35.120
really cool. And I'm curious like how
真酷。 我很好奇

98
00:03:32.840 --> 00:03:37.600
was this model trained? Like did we do
这个模型是如何训练的？ 我们是不是做了

99
00:03:35.120 --> 00:03:40.560
anything specific to like make it so
什么特别的事情，让它这么

100
00:03:37.600 --> 00:03:43.040
good at like catching bugs? Yeah, so it
擅长捕捉昆虫？ 是的，这

101
00:03:40.560 --> 00:03:45.080
is part of the Codex training, but we
是 Codex 培训的一部分，但我们

102
00:03:43.040 --> 00:03:47.720
added some specific tasks in which we
添加了一些具体的任务，

103
00:03:45.080 --> 00:03:50.120
wanted to really prioritize catching
希望真正优先发现那些

104
00:03:47.720 --> 00:03:52.640
bugs that actually matter and people
真正重要且人们

105
00:03:50.120 --> 00:03:55.440
would be willing to fix in real life. We
在现实生活中愿意修复的错误。 我们

106
00:03:52.640 --> 00:03:58.200
also made sure that we aimed for very
还确保力求达到非常

107
00:03:55.440 --> 00:03:59.960
high precision rate. When we evaluated
高的准确率。 当我们将

108
00:03:58.200 --> 00:04:01.920
it against the previous generation of
其与上一代

109
00:03:59.960 --> 00:04:04.880
the models, we have shown that it has
模型进行比较时，我们发现它的

110
00:04:01.920 --> 00:04:06.240
much lower incorrect comments rate. But
错误评论率要低得多。 但

111
00:04:04.880 --> 00:04:07.960
to be fair, the most important
公平地说，最重要的

112
00:04:06.240 --> 00:04:10.120
evaluation is just people using it in
评价还是看人们在

113
00:04:07.960 --> 00:04:12.200
practice and it finding the real bugs
实际使用中能否发现真正的错误，

114
00:04:10.120 --> 00:04:14.840
and simultaneously not being annoying by
同时又不会因为

115
00:04:12.200 --> 00:04:16.959
outputting too much comments. Mhm, yeah.
输出过多评论而令人厌烦。 嗯，是的。

116
00:04:14.840 --> 00:04:19.160
So, you showed us like a couple examples
所以，你给我们展示了几个

117
00:04:16.959 --> 00:04:20.959
with GPT-OSS. Now, I'd love to touch
GPT-OSS 的例子。 现在，我想

118
00:04:19.160 --> 00:04:23.360
more on like how we use it internally at
更详细地谈谈我们在 OpenAI 内部是如何使用它的

119
00:04:20.959 --> 00:04:25.440
OpenAI. Yeah, we've already used it for
。 是的，我们已经使用了

120
00:04:23.360 --> 00:04:27.480
a while, and we have gotten a lot of
一段时间，并且有很多

121
00:04:25.440 --> 00:04:30.600
examples of it really saving us from
例子表明它确实帮助我们避免了一些

122
00:04:27.480 --> 00:04:32.760
having critical issues. So, it saved us
重大问题。 因此，它避免了我们

123
00:04:30.600 --> 00:04:35.520
from having some important training run
遇到一些重要的训练运行

124
00:04:32.760 --> 00:04:37.960
bugs that would potentially delayed some
错误，这些错误可能会延迟一些

125
00:04:35.520 --> 00:04:40.200
important model releases or some
重要的模型发布或一些仅凭

126
00:04:37.960 --> 00:04:42.200
configurations that would not be

127
00:04:40.200 --> 00:04:44.800
normally visible just from the diff
差异通常无法看到的配置

128
00:04:42.200 --> 00:04:47.080
alone. It also allows us to more
。 这也使我们能够更有

129
00:04:44.800 --> 00:04:49.880
confidently contribute to the code bases
信心地为我们不太熟悉的代码库做出贡献

130
00:04:47.080 --> 00:04:52.400
that we're not fully familiar with. So,
。

131
00:04:49.880 --> 00:04:54.920
for example, here we have Alex, our
例如，这里有我们的

132
00:04:52.400 --> 00:04:57.200
Codex PM, contributing towards the VS
Codex 项目经理 Alex，他正在为 VS

133
00:04:54.920 --> 00:04:59.520
Code extension Yep. and implementing a
Code 扩展程序贡献力量。 并实施

134
00:04:57.200 --> 00:05:02.640
change. Code review model decided that
变革。 代码审查模型认定这

135
00:04:59.520 --> 00:05:04.160
it's not the correct way to implement
不是正确的实现方式

136
00:05:02.640 --> 00:05:06.440
it. Right, it sounds like it caught a
。 没错，听起来像是

137
00:05:04.160 --> 00:05:09.720
bug in terms of like removing a React

138
00:05:06.440 --> 00:05:12.440
prop here with the CSS. Yeah, it was not
CSS 中移除 React 属性时出现了 bug。 是的，如果

139
00:05:09.720 --> 00:05:14.680
really possible to spot this bug without
不了解整个代码库，就很难发现这个漏洞

140
00:05:12.440 --> 00:05:16.560
understanding of the broader code base

141
00:05:14.680 --> 00:05:18.360
here. But then, I love Alexi's follow-up
。 不过，我也很喜欢 Alexi 的后续作品

142
00:05:16.560 --> 00:05:19.720
as well. At Codex, fair enough, fix it
。 如果 Codex 愿意，那就没问题了，

143
00:05:18.360 --> 00:05:21.680
up cuz you can keep on going with this
因为你可以继续进行这个

144
00:05:19.720 --> 00:05:23.960
conversation and and ask Codex to take
对话，并要求 Codex 接管

145
00:05:21.680 --> 00:05:26.000
it over. Yeah, after code review bot
它。 是的，在代码审查机器人

146
00:05:23.960 --> 00:05:28.320
produces a finding, you can always ask
发现问题后，您可以随时要求

147
00:05:26.000 --> 00:05:30.720
Codex to trigger a new task and actually
Codex 触发一个新任务并实际

148
00:05:28.320 --> 00:05:32.080
fix it, which is a very nice workflow to
修复它，这是一个非常好的工作流程

149
00:05:30.720 --> 00:05:34.040
do. Yeah, that's really amazing and
。 是的，这真的很了不起，

150
00:05:32.080 --> 00:05:36.040
really the vision of having Codex at any
Codex 能够在任何

151
00:05:34.040 --> 00:05:38.120
point and any surface as your teammate
时候、任何表面上作为你的队友

152
00:05:36.040 --> 00:05:39.760
that's able to kind of do work for you.
为你效力，这才是真正的愿景。

153
00:05:38.120 --> 00:05:42.240
And what I love about like Codex code

154
00:05:39.760 --> 00:05:44.320
review here in this case is that you may
在这种情况下，我喜欢 Codex 代码审查的一点是，

155
00:05:42.240 --> 00:05:47.640
have like amazing engineers on your
你的团队可能拥有非常优秀的工程师

156
00:05:44.320 --> 00:05:50.240
team, but they may not have like many
，但他们可能没有很多

157
00:05:47.640 --> 00:05:52.680
hours to spend to kind of not just look
时间去仔细查看

158
00:05:50.240 --> 00:05:54.360
at a diff, but like run every possible
差异，而是在脑海中模拟每一种可能的

159
00:05:52.680 --> 00:05:56.680
scenario in their head. And here, you
场景。 而在这里，

160
00:05:54.360 --> 00:05:58.240
have Codex that's able to do that in its
Codex 能够按照自己的节奏做到这一点

161
00:05:56.680 --> 00:06:00.040
own time. And one thing I wanted to
。 还有一点我想

162
00:05:58.240 --> 00:06:02.200
touch on as well is that we now have
提一下，那就是我们现在有了

163
00:06:00.040 --> 00:06:04.840
like agents.md, right? This like open
像 agents.md 这样的工具，对吧？ 这就像一个开放

164
00:06:02.200 --> 00:06:06.200
format for coding agents, including
格式，供编码代理（包括

165
00:06:04.840 --> 00:06:07.800
Codex,
Codex）

166
00:06:06.200 --> 00:06:10.320
to kind of like follow some specific
遵循一些具体的

167
00:06:07.800 --> 00:06:12.240
instructions. Have you like used
指示。 你是否像你一样使用

168
00:06:10.320 --> 00:06:14.400
agents.md like in your case to kind of
agents.md 文件，为

169
00:06:12.240 --> 00:06:16.240
give Codex code review some extra
Codex 代码审查提供一些额外的

170
00:06:14.400 --> 00:06:18.320
instructions? We actually trained the
说明？ 我们特意训练了该

171
00:06:16.240 --> 00:06:20.600
model specifically to be steerable
模型，使其能够

172
00:06:18.320 --> 00:06:23.080
either with with custom user
通过自定义用户

173
00:06:20.600 --> 00:06:24.920
instructions or look for agents.md
指令或查找

174
00:06:23.080 --> 00:06:27.720
within the code base.
代码库中的 agents.md 文件进行控制。

175
00:06:24.920 --> 00:06:29.920
So, if you add some custom code review
因此，如果您在软件包中添加一些自定义代码审查

176
00:06:27.720 --> 00:06:31.840
guidelines to your package, that would
指南，这将

177
00:06:29.920 --> 00:06:33.840
help model to understand the code base,
有助于模型理解代码库，

178
00:06:31.840 --> 00:06:35.600
but also potential requirements about
但也可能对代码审查中

179
00:06:33.840 --> 00:06:37.560
what it should pay special attention to
应该特别注意哪些方面，

180
00:06:35.600 --> 00:06:40.240
in code review, or maybe what kind of
或者哪些类型的

181
00:06:37.560 --> 00:06:42.520
problems to ignore and don't bother your
问题应该忽略，不要打扰您的

182
00:06:40.240 --> 00:06:44.680
developers about. That's awesome. Uh you
开发人员提出潜在要求。 太棒了。 呃，你

183
00:06:42.520 --> 00:06:46.560
can even like ask some custom special
甚至可以询问一些

184
00:06:44.680 --> 00:06:49.040
instructions about the style it responds
关于它所响应的风格的特殊定制说明

185
00:06:46.560 --> 00:06:51.280
to. So, for example, since I needed a
。 例如，因为我需要更多的

186
00:06:49.040 --> 00:06:53.400
little bit more validation, I wanted
肯定，所以我希望

187
00:06:51.280 --> 00:06:55.280
Codex to tell me every time I make a bug
Codex 在我每次犯错时都告诉我，

188
00:06:53.400 --> 00:06:58.080
that I'm still an amazing programmer.
我仍然是一位了不起的程序员。

189
00:06:55.280 --> 00:06:59.440
That's awesome, and you are.
太棒了，你确实很棒。

190
00:06:58.080 --> 00:07:01.800
Uh what we've been looking at here so
嗯，到目前为止，我们一直在研究的是

191
00:06:59.440 --> 00:07:04.040
far is been Codex reviewing code in the
Codex 在云端进行代码审查

192
00:07:01.800 --> 00:07:08.000
cloud. But just recently, we also
。 但就在最近，我们还在

193
00:07:04.040 --> 00:07:10.080
introduced review in the Codex CLI. So,
Codex CLI 中引入了审阅功能。 所以，

194
00:07:08.000 --> 00:07:12.360
you can have a review in the terminal as
你也可以在终端机上进行复习

195
00:07:10.080 --> 00:07:15.040
well. So, very often, you want to review
。 所以，很多时候，你需要在

196
00:07:12.360 --> 00:07:17.640
the code already before it makes it into
代码上传到 GitHub 之前先对其进行审查

197
00:07:15.040 --> 00:07:20.480
the GitHub. For that purpose, CLI is
。 为此，CLI 非常

198
00:07:17.640 --> 00:07:23.040
perfect. And it also can execute more
完美。 它还可以

199
00:07:20.480 --> 00:07:25.760
things locally on your computer. So, you
在你的电脑本地执行更多操作。 所以，你

200
00:07:23.040 --> 00:07:27.720
could just /review
可以直接使用 /review 命令

201
00:07:25.760 --> 00:07:29.280
in order to tell the model to review
来告诉模型查看

202
00:07:27.720 --> 00:07:31.240
your current changes. And we're going to
你当前的更改。 接下来几周，我们将对

203
00:07:29.280 --> 00:07:32.800
improve on this feature a lot over the
这个功能进行大幅改进

204
00:07:31.240 --> 00:07:34.360
next weeks. So, it's basically like
。 所以，这基本上就像是在

205
00:07:32.800 --> 00:07:36.080
making sure all of your changes that

206
00:07:34.360 --> 00:07:38.600
you're introducing locally don't have

207
00:07:36.080 --> 00:07:41.600
like bugs before you submit them to to a
提交 PR 之前，确保你在本地引入的所有更改都没有 bug

208
00:07:38.600 --> 00:07:43.960
PR. Exactly. Amazing. Well, there you
。 确切地。 惊人的。 好了，这就是

209
00:07:41.600 --> 00:07:45.640
have it, Codex code review.
Codex 代码审查的全部内容。

210
00:07:43.960 --> 00:07:47.640
So, with Codex, you now have an amazing
因此，有了 Codex，您现在就拥有了一个出色的

211
00:07:45.640 --> 00:07:49.520
coding agent to pair with locally in the
编码代理，可以在本地

212
00:07:47.640 --> 00:07:51.680
terminal or in your code editor,
终端或代码编辑器中使用，也可以

213
00:07:49.520 --> 00:07:54.120
an awesome teammate to send tasks to in

214
00:07:51.680 --> 00:07:56.720
the cloud at any time. You also have the
随时在云端向一个很棒的队友发送任务。 您还可以

215
00:07:54.120 --> 00:07:59.480
ability for Codex to review your changes
让 Codex 在您的同事看到之前，先在本地审查您的更改

216
00:07:56.720 --> 00:08:01.160
locally or your PRs on GitHub before
或 GitHub 上的 PR

217
00:07:59.480 --> 00:08:03.120
your co-workers even get to them. It's
。 它将

218
00:08:01.160 --> 00:08:05.240
going to help you catch bugs before they
帮助您在漏洞

219
00:08:03.120 --> 00:08:07.040
hit production, and we can't wait to see
进入生产环境之前将其发现，我们迫不及待地想看看

220
00:08:05.240 --> 00:08:08.920
how that's going to accelerate your team
它将如何加快您的团队速度，

221
00:08:07.040 --> 00:08:10.520
and ultimately help you ship better and
并最终帮助您交付更好、更

222
00:08:08.920 --> 00:08:13.240
safer products.
安全的产品。

223
00:08:10.520 --> 00:08:13.240
Thanks for watching.
感谢观看。

224
00:08:14.080 --> 00:08:17.720
Back to work. Indeed.
回去工作。 的确。
