From 3893a8e379f60d7f4b89b1c40c1fff6e3b40edb5 Mon Sep 17 00:00:00 2001 From: anaxceron Date: Tue, 19 Dec 2023 16:34:34 -0500 Subject: [PATCH] adding V3 N/A label instructions Signed-off-by: anaxceron --- .github/pr-comments/for-labeller.md | 1 + .github/pr-comments/for-writer.md | 1 + 2 files changed, 2 insertions(+) diff --git a/.github/pr-comments/for-labeller.md b/.github/pr-comments/for-labeller.md index fcc327b87c..34a27078a8 100644 --- a/.github/pr-comments/for-labeller.md +++ b/.github/pr-comments/for-labeller.md @@ -3,6 +3,7 @@ - [ ] Add the label `review: doc`. - [ ] Identify your content topic with a label. (Examples: `area: apiml`, `area: cli`, `area: install and config`, etc.) - [ ] Specify the major Zowe release(s) for your content. (Examples: `release: V1`, `release: V2`, `release: V3`) + - [ ] If adding content that needs to be removed from V3 documentation, add the `V3 N/A` tag. - [ ] Select the `master` branch if your PR updates content that is on the **live site**. Select `docs-staging` if your PR updates content for a future release. - [ ] Notify the Doc Squad about this PR. If you don't know whom should review your content, message the [#zowe-doc](https://openmainframeproject.slack.com/archives/CC961JYMQ) Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer. diff --git a/.github/pr-comments/for-writer.md b/.github/pr-comments/for-writer.md index efc69f9e9e..85f21afaa0 100644 --- a/.github/pr-comments/for-writer.md +++ b/.github/pr-comments/for-writer.md @@ -3,6 +3,7 @@ - [ ] Add the label `review: sme` if an SME needs to check your content. - [ ] Identify your content topic with a label. (Examples: `area: apiml`, `area: cli`, `area: install and config`, etc.) - [ ] Specify the major Zowe release(s) for your content. (Examples: `release: V1`, `release: V2`, `release: V3`) + - [ ] If adding content that needs to be removed from V3 documentation, add the `V3 N/A` tag. - [ ] Link any [Doc Issues](https://github.com/zowe/docs-site/issues) related to this PR. - [ ] Fix broken links found in your content areas. - [ ] Notify the SME to review this PR (if applicable).