chore: update issue/pr templates

This commit is contained in:
cedoor
2022-06-24 12:52:22 +02:00
parent 1335a03990
commit de9e397377
5 changed files with 36 additions and 63 deletions

View File

@@ -1,8 +1,10 @@
---
name: Bug report
name: "\U0001F41E Bug"
about: Create a report to help us improve
title: ""
labels: ""
title: ''
labels: "bug \U0001F41B"
assignees: ''
---
**Describe the bug**
@@ -24,9 +26,9 @@ If applicable, add screenshots to help explain your problem.
**Technologies (please complete the following information):**
- Node.js version
- NPM version
- Browser
- Node.js version
- NPM version
- Solidity version
**Additional context**
Add any other context about the problem here.

View File

@@ -1,8 +1,10 @@
---
name: Feature request
about: Suggest an idea for one of the existing packages
title: ""
labels: ""
name: "\U0001F680 Feature"
about: Suggest an idea for Semaphore
title: ''
labels: 'feature :rocket:'
assignees: ''
---
**Is your feature request related to a problem? Please describe.**

14
.github/ISSUE_TEMPLATE/---package.md vendored Normal file
View File

@@ -0,0 +1,14 @@
---
name: "\U0001F4E6 Package"
about: Propose a new Semaphore package
title: ''
labels: 'feature :rocket:'
assignees: ''
---
**Describe the package you'd like**
A clear and concise description of the type of package you have in mind.
**Additional context**
Add any other context about the package here.

View File

@@ -1,18 +0,0 @@
---
name: Package request
about: Suggest an idea for this project
title: ""
labels: ""
---
**Describe the package**
A clear and concise description of what the package should be.
**Describe why it may be useful**
A clear and concise description of the context in which this package could be used and why it may be usefulp.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.

View File

@@ -1,43 +1,16 @@
<!-- Please refer to our contributing documentation for any questions on submitting a pull request -->
<!--- Provide a general summary of your changes in the Title above -->
## Pull request checklist
## Description
Please check if your PR fulfills the following requirements:
<!--- Describe your changes in detail -->
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
- [ ] Build (`yarn build`) was run locally and any changes were pushed
- [ ] Lint (`yarn lint`) has passed locally and any fixes were made for failures
## Related Issue
## Pull request type
<!-- Please do not submit updates to dependencies unless it fixes an issue. -->
<!-- Please try to limit your pull request to one type, submit multiple pull requests if needed. -->
Please check the type of change your PR introduces:
- [ ] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):
## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Issue Number: N/A
## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by this PR. -->
-
-
-
<!--- This project 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 -->
<!--- Please link to the issue here: -->
## Does this introduce a breaking change?