@@ -83,21 +83,21 @@ for the current list of chairpersons.
83
83
<!--
84
84
## SIG Docs teams and automation
85
85
86
- Automation in SIG Docs relies on two different mechanisms for automation :
87
- GitHub groups and OWNERS files.
86
+ Automation in SIG Docs relies on two different mechanisms:
87
+ GitHub teams and OWNERS files.
88
88
-->
89
89
## SIG Docs 团队和自动化 {#sig-docs-teams-and-automation}
90
90
91
- SIG 文档中的自动化服务依赖于两种不同的自动化机制 :
92
- GitHub 组和 OWNERS 文件。
91
+ SIG 文档中的自动化服务依赖于两种不同的机制 :
92
+ GitHub 团队和 OWNERS 文件。
93
93
94
94
<!--
95
95
### GitHub teams
96
96
97
97
There are two categories of SIG Docs [teams](https://github.com/orgs/kubernetes/teams?query=sig-docs) on GitHub:
98
98
99
99
- `@sig-docs-{language}-owners` are approvers and leads
100
- - `@sig-docs-{language}-reviewers ` are reviewers
100
+ - `@sig-docs-{language}-reviews ` are reviewers
101
101
102
102
Each can be referenced with their `@name` in GitHub comments to communicate with
103
103
everyone in that group.
@@ -110,7 +110,7 @@ the automation uses information from `OWNERS` files.
110
110
GitHub 上有两类 SIG Docs 团队:
111
111
112
112
- ` @sig-docs-{language}-owners ` 包含批准人和牵头人
113
- - ` @sig-docs-{language}-reviewers ` 包含评阅人
113
+ - ` @sig-docs-{language}-reviews ` 包含评阅人
114
114
115
115
可以在 GitHub 的评论中使用团队的名称 ` @name ` 来与团队成员沟通。
116
116
@@ -123,13 +123,13 @@ GitHub 上有两类 SIG Docs 团队:
123
123
The Kubernetes project uses an automation tool called prow for automation
124
124
related to GitHub issues and pull requests. The
125
125
[Kubernetes website repository](https://github.com/kubernetes/website) uses
126
- two [prow plugins](https://github.com/kubernetes/test-infra/blob /master/prow/plugins):
126
+ two [prow plugins](https://github.com/kubernetes/test-infra/tree /master/prow/plugins):
127
127
-->
128
128
### OWNERS 文件和扉页 {#owners-files-and-front-matter}
129
129
130
130
Kubernetes 项目使用名为 prow 的自动化工具来自动处理 GitHub issue 和 PR。
131
131
[ Kubernetes website 仓库] ( https://github.com/kubernetes/website ) 使用了两个
132
- [ prow 插件] ( https://github.com/kubernetes/test-infra/blob /master/prow/plugins ) :
132
+ [ prow 插件] ( https://github.com/kubernetes/test-infra/tree /master/prow/plugins ) :
133
133
134
134
- blunderbuss
135
135
- approve
@@ -150,7 +150,7 @@ how prow works within the repository.
150
150
An OWNERS file contains a list of people who are SIG Docs reviewers and
151
151
approvers. OWNERS files can also exist in subdirectories, and can override who
152
152
can act as a reviewer or approver of files in that subdirectory and its
153
- descendents . For more information about OWNERS files in general, see
153
+ descendants . For more information about OWNERS files in general, see
154
154
[OWNERS](https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md).
155
155
-->
156
156
OWNERS 文件包含 SIG Docs 评阅人和批准人的列表。
@@ -190,7 +190,7 @@ SIG Docs approvers. Here's how it works.
190
190
- Any Kubernetes member can add the `lgtm` label by adding a `/lgtm` comment.
191
191
- Only SIG Docs approvers can merge a pull request
192
192
by adding an `/approve` comment. Some approvers also perform additional
193
- specific roles, such as [PR Wrangler](/docs/contribute/advanced#be-the- pr-wrangler-for-a-week ) or
193
+ specific roles, such as [PR Wrangler](/docs/contribute/participate/ pr-wranglers/ ) or
194
194
[SIG Docs chairperson](#sig-docs-chairperson).
195
195
-->
196
196
## PR 是怎样被合并的 {#how-merging-works}
0 commit comments