From 6611472b4802d75497c2c8f8def84ed5f6b5000f Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Mon, 5 Dec 2022 17:25:12 +0100 Subject: [PATCH] Mention release notes in automated comment for `github/docs-internal` pull requests (#33200) --- .github/workflows/hubber-contribution-help.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/hubber-contribution-help.yml b/.github/workflows/hubber-contribution-help.yml index 9877c5ec99..cf33f606f9 100644 --- a/.github/workflows/hubber-contribution-help.yml +++ b/.github/workflows/hubber-contribution-help.yml @@ -42,6 +42,7 @@ jobs: gh pr comment $PR --body "Thanks so much for opening this PR and contributing to GitHub Docs! - 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." env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}