Merge pull request #48172 from my-git9/pp-11579

k8s-ci-robot · web-flow · commit e657ca6866a6 · 2024-10-04T11:58:27.000+01:00
[zh-cn]sync pr-wranglers linkchecker/README
diff --git a/content/zh-cn/docs/contribute/participate/pr-wranglers.md b/content/zh-cn/docs/contribute/participate/pr-wranglers.md
@@ -18,8 +18,8 @@ for the repository.
 This section covers the duties of a PR wrangler. For more information on giving good reviews,
 see [Reviewing changes](/docs/contribute/review/).
 -->
-SIG Docs 的[批准人（Approver）](/zh-cn/docs/contribute/participate/roles-and-responsibilities/#approvers)们每周轮流负责
-[管理仓库的 PR](https://github.com/kubernetes/website/wiki/PR-Wranglers)。
+SIG Docs 的[批准人（Approver）](/zh-cn/docs/contribute/participate/roles-and-responsibilities/#approvers)
+们每周轮流负责[管理仓库的 PR](https://github.com/kubernetes/website/wiki/PR-Wranglers)。
 
 本节介绍 PR 管理者的职责。关于如何提供较好的评审意见，
 可参阅[评审变更](/zh-cn/docs/contribute/review/)。
@@ -33,7 +33,8 @@ Each day in a week-long shift as PR Wrangler:
 - Review [open pull requests](https://github.com/kubernetes/website/pulls) for quality
   and adherence to the [Style](/docs/contribute/style/style-guide/) and
   [Content](/docs/contribute/style/content-guide/) guides.
-    - Start with the smallest PRs (`size/XS`) first, and end with the largest (`size/XXL`). Review as many PRs as you can.
+  - Start with the smallest PRs (`size/XS`) first, and end with the largest (`size/XXL`).
+    Review as many PRs as you can.
 -->
 ## 职责 {#duties}
 
@@ -47,15 +48,15 @@ Each day in a week-long shift as PR Wrangler:
     PR（`size/XXL`），尽可能多地评审 PR。
 <!-- 
 - Make sure PR contributors sign the [CLA](https://github.com/kubernetes/community/blob/master/CLA.md).
-    - Use [this](https://github.com/zparnold/k8s-docs-pr-botherer) script to remind contributors
-      that haven't signed the CLA to do so.
+  - Use [this](https://github.com/zparnold/k8s-docs-pr-botherer) script to remind contributors
+    that haven't signed the CLA to do so.
 - Provide feedback on changes and ask for technical reviews from members of other SIGs.
-    - Provide inline suggestions on the PR for the proposed content changes.
-    - If you need to verify content, comment on the PR and request more details.
-    - Assign relevant `sig/` label(s).
-    - If needed, assign reviewers from the `reviewers:` block in the file's front matter.
-    - You can also tag a [SIG](https://github.com/kubernetes/community/blob/master/sig-list.md)
-      for a review by commenting `@kubernetes/<sig>-pr-reviews` on the PR.
+  - Provide inline suggestions on the PR for the proposed content changes.
+  - If you need to verify content, comment on the PR and request more details.
+  - Assign relevant `sig/` label(s).
+  - If needed, assign reviewers from the `reviewers:` block in the file's front matter.
+  - You can also tag a [SIG](https://github.com/kubernetes/community/blob/master/sig-list.md)
+    for a review by commenting `@kubernetes/<sig>-pr-reviews` on the PR.
 -->
 - 确保贡献者签署 [CLA](https://github.com/kubernetes/community/blob/master/CLA.md)。
   - 使用[此脚本](https://github.com/zparnold/k8s-docs-pr-botherer)自动提醒尚未签署
@@ -69,13 +70,13 @@ Each day in a week-long shift as PR Wrangler:
     [SIG](https://github.com/kubernetes/community/blob/master/sig-list.md) 来评审。
 <!-- 
 - Use the `/approve` comment to approve a PR for merging. Merge the PR when ready.
-    - PRs should have a `/lgtm` comment from another member before merging.
-    - Consider accepting technically accurate content that doesn't meet the
-      [style guidelines](/docs/contribute/style/style-guide/). As you approve the change,
-      open a new issue to address the style concern. You can usually write these style fix
-      issues as [good first issues](https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue).
-    - Using style fixups as good first issues is a good way to ensure a supply of easier tasks
-      to help onboard new contributors.
+  - PRs should have a `/lgtm` comment from another member before merging.
+  - Consider accepting technically accurate content that doesn't meet the
+    [style guidelines](/docs/contribute/style/style-guide/). As you approve the change,
+    open a new issue to address the style concern. You can usually write these style fix
+    issues as [good first issues](https://kubernetes.dev/docs/guide/help-wanted/#good-first-issue).
+  - Using style fixups as good first issues is a good way to ensure a supply of easier tasks
+    to help onboard new contributors.
 -->
 - 使用 `/approve` 评论来批准可以合并的 PR，在 PR 就绪时将其合并。
   - PR 在被合并之前，应该有来自其他成员的 `/lgtm` 评论。
@@ -87,7 +88,8 @@ Each day in a week-long shift as PR Wrangler:
     这有助于接纳新的贡献者。
 
 <!--
-- Also check for pull requests against the [reference docs generator](https://github.com/kubernetes-sigs/reference-docs) code, and review those (or bring in help).
+- Also check for pull requests against the [reference docs generator](https://github.com/kubernetes-sigs/reference-docs)
+  code, and review those (or bring in help).
 - Support the [issue wrangler](/docs/contribute/participate/issue-wrangler/) to
   triage and tag incoming issues daily.
   See [Triage and categorize issues](/docs/contribute/review/for-approvers/#triage-and-categorize-issues)
@@ -101,11 +103,12 @@ Each day in a week-long shift as PR Wrangler:
 
 {{< note >}}
 <!--
-PR wrangler duties do not apply to localization PRs (non-English PRs). 
-Localization teams have their own processes and teams for reviewing their language PRs. 
-However, it's often helpful to ensure language PRs are labeled correctly, 
-review small non-language dependent PRs (like a link update), 
-or tag reviewers or contributors in long-running PRs (ones opened more than 6 months ago and have not been updated in a month or more).
+PR wrangler duties do not apply to localization PRs (non-English PRs).
+Localization teams have their own processes and teams for reviewing their language PRs.
+However, it's often helpful to ensure language PRs are labeled correctly,
+review small non-language dependent PRs (like a link update),
+or tag reviewers or contributors in long-running PRs
+(ones opened more than 6 months ago and have not been updated in a month or more).
 -->
 PR 管理者的职责不适用于本地化 PR（非英语 PR）。
 本地化团队有自己的流程和团队来审查其语言 PR。
@@ -201,10 +204,11 @@ These queries exclude localization PRs. All queries are against the main branch
 Reviews and approvals are one tool to keep our PR queue short and current. Another tool is closure.
 
 Close PRs where:
+
 - The author hasn't signed the CLA for two weeks.
 
-    Authors can reopen the PR after signing the CLA. This is a low-risk way to make
-    sure nothing gets merged without a signed CLA.
+  Authors can reopen the PR after signing the CLA. This is a low-risk way to make
+  sure nothing gets merged without a signed CLA.
 
 - The author has not responded to comments or feedback in 2 or more weeks.
 
@@ -237,7 +241,7 @@ and closes them. PR wranglers should close issues after 14-30 days of inactivity
 -->
 一个名为 [`k8s-ci-robot`](https://github.com/k8s-ci-robot) 的自动服务会在 Issue 停滞 90
 天后自动将其标记为过期；然后再等 30 天，如果仍然无人过问，则将其关闭。
-PR 管理者应该在 issues 处于无人过问状态 14-30 天后关闭它们。
+PR 管理者应该在 Issue 处于无人过问状态 14-30 天后关闭它们。
 {{< /note >}}
 
 <!--
@@ -273,7 +277,7 @@ The program was introduced to help new contributors understand the PR wrangling
   PR 管理轮值表，然后注册报名。
 
 - 其他人可以通过 [#sig-docs Slack 频道](https://kubernetes.slack.com/messages/sig-docs)申请成为指定
-  PR 管理者某一周的影子。可以随时咨询 (`@bradtopol`) 或某一位
+  PR 管理者某一周的影子。可以随时咨询（`@bradtopol`）或某一位
   [SIG Docs 联席主席/主管](https://github.com/kubernetes/community/tree/master/sig-docs#leadership)。
 
 - 注册成为一名 PR 管理者的影子时，
diff --git a/content/zh-cn/docs/doc-contributor-tools/linkchecker/README.md b/content/zh-cn/docs/doc-contributor-tools/linkchecker/README.md
@@ -4,7 +4,9 @@
 # 内置链接检查工具
 
 <!--
-You can use [htmltest](https://github.com/wjdp/htmltest) to check for broken links in [`/content/en/`](https://git.k8s.io/website/content/en/). This is useful when refactoring sections of content, moving pages around, or renaming files or page headers.
+You can use [htmltest](https://github.com/wjdp/htmltest) to check for broken links in
+[`/content/en/`](https://git.k8s.io/website/content/en/). This is useful when refactoring
+sections of content, moving pages around, or renaming files or page headers.
 -->
 你可以使用 [htmltest](https://github.com/wjdp/htmltest) 来检查
 [`/content/en/`](https://git.k8s.io/website/content/en/) 下面的失效链接。
@@ -16,15 +18,18 @@ You can use [htmltest](https://github.com/wjdp/htmltest) to check for broken lin
 ## 工作原理   {#how-the-tool-works}
 
 <!--
-`htmltest` scans links in the generated HTML files of the kubernetes website repository. It runs using a `make` command which does the following:
+`htmltest` scans links in the generated HTML files of the kubernetes website repository.
+It runs using a `make` command which does the following:
 -->
 `htmltest` 会扫描 Kubernetes website 仓库构建生成的 HTML 文件。通过执行 `make` 命令进行了下列操作：
 
 <!--
-- Builds the site and generates output HTML in the `/public` directory of your local `kubernetes/website` repository
+- Builds the site and generates output HTML in the `/public` directory of your
+  local `kubernetes/website` repository
 - Pulls the `wdjp/htmltest` Docker image
 - Mounts your local `kubernetes/website` repository to the Docker image
-- Scans the files generated in the `/public` directory and provides command line output when it encounters broken internal links 
+- Scans the files generated in the `/public` directory and provides command line output
+  when it encounters broken internal links 
 -->
 - 构建站点并输出 HTML 到本地 `kubernetes/website` 仓库下的 `/public` 目录中
 - 拉取 Docker 镜像 `wdjp/htmltest`
@@ -37,7 +42,10 @@ You can use [htmltest](https://github.com/wjdp/htmltest) to check for broken lin
 ## 哪些链接不会检查   {#what-it-does-and-doesnot-check}
 
 <!--
-The link checker scans generated HTML files, not raw Markdown. The htmltest tool depends on a configuration file, [`.htmltest.yml`](https://git.k8s.io/website/.htmltest.yml), to determine which content to examine.
+The link checker scans generated HTML files, not raw Markdown.
+The htmltest tool depends on a configuration file,
+[`.htmltest.yml`](https://git.k8s.io/website/.htmltest.yml),
+to determine which content to examine.
 
 The link checker scans the following:
 -->
@@ -47,8 +55,10 @@ The link checker scans the following:
 该链接检查器扫描以下内容：
 
 <!--
-- All content generated from Markdown in [`/content/en/docs`](https://git.k8s.io/website/content/en/docs/) directory, excluding:
-  - Generated API references, for example https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
+- All content generated from Markdown in
+  [`/content/en/docs`](https://git.k8s.io/website/content/en/docs/) directory, excluding:
+  - Generated API references, for example
+     https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
 - All internal links, excluding:
   - Empty hashes (`<a href="#">` or `[title](#)`) and empty hrefs (`<a href="">` or `[title]()`)
   - Internal links to images and other media files
@@ -66,16 +76,18 @@ The link checker does not scan the following:
 该链接检查器不会扫描以下内容：
 
 <!--
-- Links included in the top and side nav bars, footer links, or links in a page's `<head>` section, such as links to CSS stylesheets, scripts, and meta information
+- Links included in the top and side nav bars, footer links, or links in a page's `<head>` section,
+  such as links to CSS stylesheets, scripts, and meta information
 - Top level pages and their children, for example: `/training`, `/community`, `/case-studies/adidas`
 - Blog posts
-- API Reference documentation, for example: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
+- API Reference documentation, for example
+  https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
 - Localizations
 -->
 - 包含在顶部和侧边导航栏的链接，以及页脚链接或者页面的 `<head>` 部分中的链接，例如 CSS 样式表、脚本以及元信息的链接。
 - 顶级页面及其子页面，例如：`/training`、`/community`、`/case-studies/adidas`
 - 博客文章
-- API 参考文档，例如： https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
+- API 参考文档，例如 https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/
 - 本地化内容
 
 <!--
@@ -87,6 +99,7 @@ The link checker does not scan the following:
 You must install
 -->
 必须安装：
+
 * [Docker](https://docs.docker.com/get-docker/)
 * [make](https://www.gnu.org/software/make/)
 
@@ -109,7 +122,7 @@ To run the link checker:
 
 2. 执行如下命令：
 
-   ```
+   ```shell
    make container-internal-linkcheck
    ```
 
@@ -152,8 +165,10 @@ One way to fix this is to:
 
 <!--
 1. Navigate to the Markdown file with a broken link.
-2. Using a text editor, do a full-text search (usually Ctrl+F or Command+F) for the broken link's URL, `#preserving-unknown-fields`.
-3. Fix the link. For a broken page hash (or _anchor_) link, check whether the topic was renamed or removed.
+2. Using a text editor, do a full-text search (usually Ctrl+F or Command+F) for the
+   broken link's URL, `#preserving-unknown-fields`.
+3. Fix the link. For a broken page hash (or _anchor_) link,
+   check whether the topic was renamed or removed.
 -->
 1. 转到含有失效链接的 Markdown 文件。
 2. 使用文本编辑器全文搜索失效链接的 URL（通常使用 Ctrl+F 或 Command+F）`#preserving-unknown-fields`。
