-
Notifications
You must be signed in to change notification settings - Fork 33
Add Issue template #21
Comments
@lachellel, @mrwiggins1, @GSAllewell Does this work for the issues template? If so, should we have the same template across all repos? File(s) Used for Adding/Updating Content:References (i.e. Source Docs / Files):
High-Level Description of Issue:
|
We should have a similar issue template across all repos
Just my 2cents quickly. Discuss and modify! |
We're all on the same page; Jordan and I concurred during the Playbook call Looks good to me. I can't think of anything to add. On Mon, Sep 26, 2016 at 3:37 PM, LRL notifications@github.com wrote:
Matthew R Wiggins |
GSAllewell has nothing to @dd. On Mon, Sep 26, 2016 at 3:40 PM, mrwiggins1 notifications@github.com
Tom Hallewell |
Based on the comments what about this updated example for an issue titled "FPKI Overview"? Description of Issue:
Details of Issue:
References (Docs, Links, Files):If a New Page or Content is Needed, Expected Outcomes:
Link to the Content Page for Contributors: |
Looks good @djpackham Are you going to add the ISSUE_TEMPLATE or should I add and submit a PR? https://help.github.com/articles/creating-an-issue-template-for-your-repository/ |
I will add the ISSUE_TEMPLATE and submit a PR. |
closed via #41 |
Add an Issue template
Purpose: to gather good information for each issue opened
NIST 800-63-3 (https://github.com/usnistgov/800-63-3/issues?q=is%3Aopen+is%3Aissue) has an example to review and modify
Include info decided for #20
The text was updated successfully, but these errors were encountered: