Skip to content

Commit 42e5fd4

Browse files
committed
Making template more simpler
Signed-off-by: rishi-source <[email protected]>
1 parent 64382e3 commit 42e5fd4

File tree

1 file changed

+16
-23
lines changed

1 file changed

+16
-23
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 16 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,3 @@
1-
<!--
2-
Thanks for submitting a pull request! Let's make VulnerableCode better together.
3-
Please fill out the info below to help us understand and review your changes.
4-
-->
5-
61
<!-- Delete Template sections if unneccesary -->
72
<!-- Add issue number here (We encourage you to create the Issue First) -->
83
<!-- You can also link the issue in Commit Messages -->
@@ -22,32 +17,30 @@ Fixes #(issue number)
2217
## What kind of change is this?
2318

2419
<!-- Check the boxes that apply to your PR -->
25-
* [ ] 🐛 Bug fix
26-
* [ ] New feature
27-
* [ ] 📚 Documentation update
28-
* [ ] 📥 New importer pipeline ([How to add](https://vulnerablecode.readthedocs.io/en/latest/tutorial_add_importer_pipeline.html))
29-
* [ ] 🔧 New improver pipeline ([How to add](https://vulnerablecode.readthedocs.io/en/latest/tutorial_add_improver_pipeline.html))
30-
* [ ] 🧹 Code cleanup or performance improvement
31-
* [ ] 🔄 Other: _____
20+
* [ ] Bug fix
21+
* [ ] New feature
22+
* [ ] Documentation update
23+
* [ ] New importer pipeline ([How to add](https://vulnerablecode.readthedocs.io/en/latest/tutorial_add_importer_pipeline.html))
24+
* [ ] New improver pipeline ([How to add](https://vulnerablecode.readthedocs.io/en/latest/tutorial_add_improver_pipeline.html))
25+
* [ ] Code cleanup or performance improvement
26+
* [ ] Other: _____
3227

3328
## Checklist before requesting a review
3429

35-
* [ ] I've read the [contribution guidelines](https://vulnerablecode.readthedocs.io/en/latest/contributing.html)
36-
* [ ] My code follows the project style
37-
* [ ] I've titled my PR clearly and linked the issue it resolves
38-
* [ ] I've added tests for my changes
39-
* [ ] I've updated docs if needed
40-
* [ ] I've updated the [CHANGELOG](https://github.com/aboutcode-org/vulnerablecode/blob/main/CHANGELOG.rst) if needed
41-
* [ ] My code passes all tests locally
42-
* [ ] My commits follow the [project's commit message style](https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html)
30+
* [ ] read the [contribution guidelines](https://vulnerablecode.readthedocs.io/en/latest/contributing.html)
31+
* [ ] code follows the project style
32+
* [ ] titled my PR clearly and linked the issue it resolves
33+
* [ ] added tests for my changes
34+
* [ ] updated docs if needed
35+
* [ ] updated the [CHANGELOG](https://github.com/aboutcode-org/vulnerablecode/blob/main/CHANGELOG.rst) if needed
36+
* [ ] code passes all tests locally
37+
* [ ] commits follow the [project's commit message style](https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html)
4338

4439
## AI assistance?
4540

46-
* [ ] I used AI tools (like ChatGPT, Copilot, etc.) to help with this PR
41+
* [ ] used AI tools (like ChatGPT, Copilot, etc.) to help with this PR
4742
* If yes, please share which parts: <!-- "Some code in file X," "documentation," etc. -->
4843

49-
Using AI is perfectly fine! We just need transparency so maintainers can review appropriately. This helps ensure the quality and security of our codebase.
50-
5144
## Anything else we should know?
5245

5346
<!-- Any extra context or screenshots that might help with the review -->

0 commit comments

Comments
 (0)