chore: update issue and mr templates

This commit is contained in:
Kai Armstrong 2022-09-13 14:52:07 -05:00
parent 3109ab3307
commit 1ce2b2e719
3 changed files with 66 additions and 31 deletions

View File

@ -1,25 +1,44 @@
**Description**
<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
<!---
Please read this!
**Expected Behavior vs Actual Behavior**
<!--- A clear and concise description of what should have happened and what happens instead -->
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label:
**Possible Fix**
<!--- Not obligatory, but suggest a fix or reason for the bug -->
- https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Abug
**Steps to Reproduce**
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code to reproduce, if relevant -->
1. Type this '...'
2. View the output '....'
3. See error
and verify the issue you're about to submit isn't a duplicate.
--->
### Checklist
<!-- Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version. -->
- [ ] I'm using the latest version of the extension (Run `glab --version`)
- Extension version: _Put your extension version here_
- [ ] Operating System and version: __Put your version here_
### Summary
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
### What is the current _bug_ behavior?
<!-- What actually happens -->
### What is the expected _correct_ behavior?
<!-- What you should see instead -->
### Relevant logs and/or screenshots
**Logs**
<!--- Paste the activity log from your command line -->
**Your Environment**
<!--- Include as many relevant details about the environment you experienced the bug in -->
* Version used (Run `glab --version`):
* Operating System and version:
### Possible fixes
/label ~"gh-new"
<!-- If you can, link to the line of code that might be responsible for the problem -->
/label ~"type::bug" ~"devops::create" ~"group::code review" ~"Category:Editor Extension" ~"cli"

View File

@ -1,10 +1,26 @@
**Describe the feature or problem you'd like to solve**
<!-- A clear and concise description of what the feature or problem is. Ex. I'm always frustrated when [...] so having [...] -->
<!---
Please read this!
**Propose a Solution**
<!-- A clear and concise description of what you want to happen and alternatives you have considered. -->
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "feature" label:
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
- https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Afeature
/label ~"gh-new"
and verify the issue you're about to submit isn't a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->
### Proposal
<!-- How are we going to solve the problem? -->
### Further details
<!-- Include examples, use cases, benefits, goals, or any other details that will help us understand the problem better. -->
### Links / references
/label ~"type::feature" ~"devops::create" ~"group::code review" ~"Category:Editor Extension" ~"cli"

View File

@ -1,20 +1,20 @@
**Description**
## Description
<!--- Describe your changes in detail -->
**Related Issue**
## Related Issues
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
Resolves #[issue_number]
**How Has This Been Tested?**
## How has this been tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
**Screenshots (if appropriate):**
## Screenshots (if appropriate):
**Types of changes**
### Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
@ -22,4 +22,4 @@ Resolves #[issue_number]
- [ ] Documentation
- [ ] Chore (Related to CI or Packaging to platforms)
/label ~"gh-new"
/label ~"devops::create" ~"group::code review" ~"Category:Editor Extension" ~"cli"