From 36899cd93c04d76febba4be856cad0c1360d236c Mon Sep 17 00:00:00 2001 From: Sean Wei Date: Tue, 20 Sep 2022 00:21:27 +0800 Subject: [PATCH] Update some contributor page --- .../en/docs/contribute/new-content/blogs-case-studies.md | 4 ++-- content/en/docs/contribute/new-content/new-features.md | 4 ++-- content/en/docs/contribute/review/for-approvers.md | 8 ++++---- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/docs/contribute/new-content/blogs-case-studies.md b/content/en/docs/contribute/new-content/blogs-case-studies.md index 975d27737e..2656b8537a 100644 --- a/content/en/docs/contribute/new-content/blogs-case-studies.md +++ b/content/en/docs/contribute/new-content/blogs-case-studies.md @@ -85,8 +85,8 @@ To submit a blog post, follow these steps: - If you are looking for greater coordination on post release dates, coordinating with [CNCF marketing](https://www.cncf.io/about/contact/) is a more appropriate choice than submitting a blog post. - Sometimes reviews can get backed up. If you feel your review isn't getting the attention it needs, - you can reach out to the blog team via [this slack channel](https://kubernetes.slack.com/messages/sig-docs-blog/) - to ask in real time. + you can reach out to the blog team on the [`#sig-docs-blog` Slack channel](https://kubernetes.slack.com/messages/sig-docs-blog/) + to ask in real time. - Blog posts should be relevant to Kubernetes users. diff --git a/content/en/docs/contribute/new-content/new-features.md b/content/en/docs/contribute/new-content/new-features.md index d40195c32d..89ac1e1247 100644 --- a/content/en/docs/contribute/new-content/new-features.md +++ b/content/en/docs/contribute/new-content/new-features.md @@ -32,7 +32,7 @@ After you've chosen a feature to document or assist, ask about it in the `#sig-d Slack channel, in a weekly SIG Docs meeting, or directly on the PR filed by the feature SIG. If you're given the go-ahead, you can edit into the PR using one of the techniques described in -[Commit into another person's PR](/docs/contribute/review/for-approvers/#commit-into-another-persons-pr). +[Commit into another person's PR](/docs/contribute/review/for-approvers/#commit-into-another-person-s-pr). ### Find out about upcoming features @@ -117,7 +117,7 @@ When ready, populate your placeholder PR with feature documentation and change the state of the PR from draft to **ready for review**. To mark a pull request as ready for review, navigate to the merge box and click **Ready for review**. -Do your best to describe your feature and how to use it. If you need help structuring your documentation, ask in the `#sig-docs` slack channel. +Do your best to describe your feature and how to use it. If you need help structuring your documentation, ask in the `#sig-docs` Slack channel. When you complete your content, the documentation person assigned to your feature reviews it. To ensure technical accuracy, the content may also require a technical review from corresponding SIG(s). diff --git a/content/en/docs/contribute/review/for-approvers.md b/content/en/docs/contribute/review/for-approvers.md index 5d0606d60d..ece02403e7 100644 --- a/content/en/docs/contribute/review/for-approvers.md +++ b/content/en/docs/contribute/review/for-approvers.md @@ -81,14 +81,14 @@ Prow Command | Role Restrictions | Description :------------|:------------------|:----------- `/lgtm` | Organization members | Signals that you've finished reviewing a PR and are satisfied with the changes. `/approve` | Approvers | Approves a PR for merging. -`/assign` | Reviewers or Approvers | Assigns a person to review or approve a PR -`/close` | Reviewers or Approvers | Closes an issue or PR. +`/assign` | Anyone | Assigns a person to review or approve a PR +`/close` | Organization members | Closes an issue or PR. `/hold` | Anyone | Adds the `do-not-merge/hold` label, indicating the PR cannot be automatically merged. `/hold cancel` | Anyone | Removes the `do-not-merge/hold` label. {{< /table >}} -See [the Prow command reference](https://prow.k8s.io/command-help) to see the full list -of commands you can use in a PR. +To view the commands that you can use in a PR, see the +[Prow Command Reference](https://prow.k8s.io/command-help?repo=kubernetes%2Fwebsite). ## Triage and categorize issues