This is an automated email from the ASF dual-hosted git repository.
rmetzger pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d4bca48 [hotfix] Remove flinkbot mentions
d4bca48 is described below
commit d4bca486750ae684b4af15ab1988c5421d1d8002
Author: Robert Metzger <[email protected]>
AuthorDate: Wed Mar 2 20:03:37 2022 +0100
[hotfix] Remove flinkbot mentions
---
contributing/reviewing-prs.md | 26 --------------------------
contributing/reviewing-prs.zh.md | 25 -------------------------
2 files changed, 51 deletions(-)
diff --git a/contributing/reviewing-prs.md b/contributing/reviewing-prs.md
index 6ddd2c5..4fc6f09 100644
--- a/contributing/reviewing-prs.md
+++ b/contributing/reviewing-prs.md
@@ -92,30 +92,4 @@ If the pull request introduces a new feature, the feature
should be documented.
See more about how to [contribute documentation]({{ site.baseurl
}}/contributing/contribute-documentation.html).
-## Review with the @flinkbot
-
-The Flink community is using a service called
[@flinkbot](https://github.com/flinkbot) to help with the review of the pull
requests.
-
-The bot automatically posts a comment tracking the review progress for each
new pull request:
-
-```
-### Review Progress
-
-* [ ] 1. The description looks good.
-* [ ] 2. There is consensus that the contribution should go into to Flink.
-* [ ] 3. [Does not need specific attention | Needs specific attention for X |
Has attention for X by Y]
-* [ ] 4. The architectural approach is sound.
-* [ ] 5. Overall code quality is good.
-
-Please see the [Pull Request Review
Guide](https://flink.apache.org/contributing/reviewing-prs.html) if you have
questions about the review process.
-```
-
-Reviewers can instruct the bot to tick off the boxes (in order) to indicate
the progress of the review.
-
-For approving the description of the contribution, mention the bot with
`@flinkbot approve description`. This works similarly with `consensus`,
`architecture` and `quality`.
-
-For approving all aspects, put a new comment with `@flinkbot approve all` into
the pull request.
-
-The syntax for requiring attention is `@flinkbot attention @username1
[@username2 ..]`.
-
diff --git a/contributing/reviewing-prs.zh.md b/contributing/reviewing-prs.zh.md
index 44f2a72..9aa0fd4 100644
--- a/contributing/reviewing-prs.zh.md
+++ b/contributing/reviewing-prs.zh.md
@@ -89,30 +89,5 @@ title: "如何审核 Pull Request"
阅读[如何贡献文档]({{ site.baseurl
}}/zh/contributing/contribute-documentation.html)了解更多。
-## 使用 @flinkbot 进行审核
-
-Flink 社区正在使用名为 [@flinkbot](https://github.com/flinkbot) 的服务来帮助审核 pull request。
-
-针对每个新的 pull request，机器人都会自动发表评论并跟踪审核进度：
-
-```
-### Review Progress
-
-* [ ] 1. The description looks good.
-* [ ] 2. There is consensus that the contribution should go into to Flink.
-* [ ] 3. [Does not need specific attention | Needs specific attention for X |
Has attention for X by Y]
-* [ ] 4. The architectural approach is sound.
-* [ ] 5. Overall code quality is good.
-
-Please see the [Pull Request Review
Guide](https://flink.apache.org/contributing/reviewing-prs.html) if you have
questions about the review process.
-```
-
-审核人可以指示机器人（按顺序）勾选方框以指示审核的进度。
-
-用于批准贡献的描述，请使用 `@flinkbot approve description` @机器人。`consensus`、`architecture`
、 `quality` 情况的操作与之类似。
-
-要批准全部方面，请在 pull request 中添加一条带有 `@flinkbot approve all` 的新评论。
-
-提醒他人关注的语法是 `@flinkbot attention @username1 [@username2 ..]`。
