Skip to content

Commit

Permalink
Add Pull Request template
Browse files Browse the repository at this point in the history
  • Loading branch information
yashksaini-coder committed Oct 5, 2024
1 parent d10a5ed commit b669518
Showing 1 changed file with 47 additions and 0 deletions.
47 changes: 47 additions & 0 deletions .github/Pull_Request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
### Title of the Pull Request
- [ ] Have you renamed the PR Title in a meaningful way?
<!--
Examples of good PR titles:
build: (for build related changes)
chore: (for updating task runner configs etc; no production code change)
docs: (for documentation changes)
feat: (for new feature)
fix: (for bug fixes)
perf: (for performance improvements)
refactor: (for refactoring code; no production code change)
revert: (when reverting changes)
style: (changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc))
test: (when adding missing tests)
-->
### Related Issue
<!-- Replace `<issue number>` with the issue number which is fixed in this PR -->
Closes: #<issue number>

### Description
<!-- Describe the changes you made in this pull request in DETAILS-->

### Type of change

What sort of changes have you made:
<!--
Example how to mark a checkbox:-
- [x] My code follows the code style of this project.
-->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Code style update (formatting, local variables)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

### Checklist
<!--
Example how to mark a checkbox:-
- [x] My code follows the code style of this project.
-->
- [ ] My code follows the code style of this project.
- [ ] I have followed the contribution guidelines
- [ ] I have performed a self-review of my own code.
- [ ] I have ensured my changes don't generate any new warnings or errors.
- [ ] I have updated the documentation (if necessary).
- [ ] I have resolved all merge conflicts.

0 comments on commit b669518

Please sign in to comment.