From b6bf2c15db2f87d5f4f40fa2a9960f1c4b586518 Mon Sep 17 00:00:00 2001 From: Melanie Yarbrough <11952755+myarb@users.noreply.github.com> Date: Tue, 3 Jan 2023 01:28:27 -0500 Subject: [PATCH] Update hubber-contribution-help.yml (#25750) Co-authored-by: Lucas Costi --- .github/workflows/hubber-contribution-help.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/hubber-contribution-help.yml b/.github/workflows/hubber-contribution-help.yml index cf33f606f9..e2419b0ed8 100644 --- a/.github/workflows/hubber-contribution-help.yml +++ b/.github/workflows/hubber-contribution-help.yml @@ -43,7 +43,8 @@ jobs: - When you're ready for the Docs team to review this PR, add the *ready-for-doc-review* label to your PR, and it will be automatically added to the [Docs Content review board](https://github.com/orgs/github/memexes/901?layout=table&groupedBy%5BcolumnId%5D=11024). **Please factor in at least 72 hours for a review, even longer if this is a substantial change.** - If you're adding a release note, request a technical review. The Docs team will review the PR after the technical review is complete. - - If this is a major update to the docs, you might want to go back and open an [issue](https://github.com/github/docs-content/issues/new/choose) to ensure we've covered all areas of the docs in these updates. Not doing so may result in delays or inaccurate documentation." + - If your updates to the docs are more than a simple fix, you might want to go back and open an [issue](https://github.com/github/docs-content/issues/new/choose) to ensure we've covered all areas of the docs in these updates. Not doing so may result in delays or inaccurate documentation." + env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} PR: ${{ github.event.pull_request.html_url }}