Skip to content

Commit 10e3d6f

Browse files
committed
update pull req template and bug report
1 parent 02eeefc commit 10e3d6f

File tree

2 files changed

+43
-16
lines changed

2 files changed

+43
-16
lines changed

Diff for: .github/ISSUE_TEMPLATE/bug_report.md

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
**Describe the bug**
8+
9+
<!-- A clear and concise description of what the bug is. -->
10+
11+
**To Reproduce**
12+
13+
Steps to reproduce the behavior:
14+
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
<!-- A clear and concise description of what you expected to happen. -->
22+
23+
**Screenshots**
24+
<!-- If applicable, add screenshots to help explain your problem. -->
25+
26+
**Additional context**
27+
<!-- Add any other context about the problem here. -->

Diff for: .github/pull_request_template.md

+16-16
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
11
### Your checklist for this pull request
2-
🚨Please review the [guidelines for contributing](https://github.com/sanscript-tech/hacking-tools-scripts/blob/main/CONTRIBUTING.md) to this repository.<br><br>
2+
:warning: Please review the [guidelines for contributing](https://github.com/sanscript-tech/hacking-tools-scripts/blob/main/CONTRIBUTING.md) to this repository.
33

4-
Parent issue: #("mention issue no.")<br>
4+
Parent issue: #("mention issue no.")
55

66
### Type of change
77

8-
Select all that applies:<br>
9-
[ ]New feature (non-breaking change which adds functionality)<br>
10-
[ ]Bug fix (non-breaking change which fixes an issue)<br>
11-
[ ]Breaking change (fix or feature that would cause existing functionality to not work as expected)<br>
12-
[ ]This change requires a documentation update<br>
8+
**Select all that applies**:
9+
* [ ] New feature (non-breaking change which adds functionality)
10+
* [ ] Bug fix (non-breaking change which fixes an issue)
11+
* [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
* [ ] This change requires a documentation update
1313

1414
### Checklist:
1515

16-
[ ]My code follows the style guidelines(Clean Code) of this project<br>
17-
[ ]I have performed a self-review of my own code<br>
18-
[ ]I have used consistent code conventions and clear function/method/variable names<br>
19-
[ ]I have commented on my code, particularly in hard-to-understand areas<br>
20-
[ ]I have created a helpful and easy to understand README.md which contains description, requirements and use case.<br>
21-
[ ]I have added relevent screenshots if necessary<br>
22-
[ ]I have made corresponding changes to the documentation<br>
23-
[ ]My changes generate no new warnings<br>
16+
* [ ] My code follows the style guidelines(Clean Code) of this project.
17+
* [ ] I have performed a self-review of my own code.
18+
* [ ] I have used consistent code conventions and clear function/method/variable names.
19+
* [ ] I have commented on my code, particularly in hard-to-understand areas.
20+
* [ ] I have created a helpful and easy to understand README.md which contains description, requirements and use case.
21+
* [ ] I have added relevent screenshots if necessary.
22+
* [ ] I have made corresponding changes to the documentation.
23+
* [ ] My changes generate no new warnings.
2424

25-
### 💔Thank you!
25+
### :heart: Thank you!

0 commit comments

Comments
 (0)