From 55aba8e9aab6d4b9aa1a310af52c5eff1a4483e1 Mon Sep 17 00:00:00 2001 From: r12a Date: Thu, 20 Jul 2023 09:47:42 +0100 Subject: [PATCH] Update add-a-new-gap-analysis-topic.md --- .github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md b/.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md index 68e03fb..4a60010 100644 --- a/.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md +++ b/.github/ISSUE_TEMPLATE/add-a-new-gap-analysis-topic.md @@ -17,9 +17,11 @@ More: IF THIS IS NOT THE ISSUE THAT IS BEING TRACKED BY THE GAP-ANALYSIS PIPELINE, ADD A POINTER TO THAT ISSUE. THE INITIAL BRIEF INTRO SHOULD REMAIN, AND MAY BE TAILORED WITH EXAMPLES RELEVANT TO THIS LANGUAGE. YOU MAY, OPTIONALLY, ALSO ADD OTHER DETAILS BELOW IF THEY ARE SPECIFIC TO THIS LANGUAGE. THEN ADD THIS: -For more details, see [this GitHub issue](https://github.com/w3c/XXXX/issues/XX), which is being used to track this gap. + +For more details, see [this GitHub issue](https://github.com/w3c/XXXX/issues/XX), which is being used to track this gap. Please add any discussion there, and not to this issue. THEN ADD THESE 2 PARAS TO THE SECOND COMMENT FIELD AND DELETE THE REST OF THIS TEMPLATE. + _The first comment in this issue contains text that will automatically appear in one or more gap-analysis documents as a subsection with the same title as this issue. Any edits made to that comment will be immediately available in the Editor's draft of the document._ _**Please add any discussion to the GitHub issue being used to track this gap, and not to this issue**_