nasa-gcn / .github Goto Github PK

Acceptance Criteria:

• instructions to open issue before PR
• basic description
• link to issue with keywords to close
• test approach

Feature Request Details ⭐

Description

We need to standardize how we create issue and PR artifacts.

Links to feature design doc, conversations, mockups, etc.

Stakeholders

@Courey @dakota002 @swyatt7 @jak574 @lpsinger @Kirill-Vorobyev

Functional Requirements

Issue template should allow developers and non-developers to create a detailed Bug Report or Feature Request
Pull Request template should allow developers to fill out a form and not forget key details when submitting a PR

Non-functional Requirements

Issue template should not take more than 5 minutes to fill out.
Pull request template should not take more than 10 minutes to fill out.

Acceptance Criteria

When a user creates an issue, the issue template should appear automatically.
When a user submits a Pull Request, the PR template should appear automatically.

Note: currently not possible to test because this initial issue/PR will add the templates.

          I'd rather automate the assignment of reviewers using CODEOWNERS, instead of requiring people to fill that in manually.

Originally posted by @lpsinger in #7 (comment)