ch0ic3/cutter
1
0
Fork 0
mirror of https://github.com/rizinorg/cutter.git synced 2024-12-18 10:56:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update templates to hide instructions from final post (#1245)

Browse Source
This commit is contained in:
Itay Cohen 2019-03-07 07:26:50 +02:00 committed by GitHub
parent d46ff14a21
commit e3ddbf6255
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 27 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
.github/ISSUE_TEMPLATE/bug_report.md vendored
View File

@ -10,9 +10,11 @@ about: Create a report to help us improve
* File format: * File format:
**Describe the bug** **Describe the bug**
A clear and concise description of what the bug is.
<!-- A clear and concise description of what the bug is. -->
**To Reproduce** **To Reproduce**
Steps to reproduce the behavior: Steps to reproduce the behavior:
1. Go to '...' 1. Go to '...'
2. Click on '....' 2. Click on '....'
@ -20,10 +22,15 @@ Steps to reproduce the behavior:
4. See error 4. See error
**Expected behavior** **Expected behavior**
A clear and concise description of what you expected to happen.
<!-- A clear and concise description of what you expected to happen. -->
**Screenshots** **Screenshots**
If applicable, add screenshots to help explain your problem.
<!-- If applicable, add screenshots to help explain your problem. -->
**Additional context** **Additional context**
Add any other context about the problem here.
<!-- Add any other context about the problem here. -->

14
.github/ISSUE_TEMPLATE/feature_request.md vendored
View File

@ -5,14 +5,18 @@ about: Suggest an idea for this project
--- ---
**Is your feature request related to a problem? Please describe.** **Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
**Describe the solution you'd like** **Describe the solution you'd like**
A clear and concise description of what you want to happen.
For UI requests, don't hesitate to post some draws. <!-- A clear and concise description of what you want to happen.
For UI requests, don't hesitate to post some draws. -->
**Describe alternatives you've considered** **Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Additional context** **Additional context**
Add any other context or screenshots about the feature request here.
<!-- Add any other context or screenshots about the feature request here. -->

14
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,17 +1,17 @@
*Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.* <!-- *Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.*
Please provide enough information so that others can review your pull request: Please provide enough information so that others can review your pull request:
Explain the **details** for making this change. What existing problem does the pull request solve? Explain the **details** for making this change. What existing problem does the pull request solve? -->
**Test plan (required)** **Test plan (required)**
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. <!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI. -->
**Code formatting** <!-- **Code formatting**
Make sure you ran astyle on your code before making the PR. Check our contribution guidelines here: https://cutter.re/docs/code.html -->
Make sure you ran astyle on your code before making the PR. Check our contribution guidelines here: https://cutter.re/docs/code.html
**Closing issues** **Closing issues**
Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). <!-- put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->