Skip to content

Commit 6d656c8

Browse files
chore: add pull request template
1 parent 19210c2 commit 6d656c8

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
<!-- This is a pull request template, you do not need to uncomment or remove the comments, they won't show up in the PR text.
2+
3+
Your Pull Request name should start with one of the following tags
4+
feat: Adding a new feature
5+
refactor: A code change that doesn't change behavior (it doesn't add anything and doesn't fix anything)
6+
fix: For bug fixes that affect the end-user
7+
chore: For small tasks
8+
docs: For documentation
9+
ci: For updating CI configuration
10+
test: For adding tests
11+
i18n: For updating any translations
12+
regression: Issues created/reported/fixed during the development phase. kind of problem that never existed in production and that we don't need to list in a changelog for the end user
13+
-->
14+
15+
## Proposed changes
16+
<!--
17+
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
18+
If it fixes a bug or resolves a feature request, be sure to link to that issue below.
19+
This description won't be displayed to our end users in the release notes, so feel free to add as much technical context as needed.
20+
If the changes introduced in this pull request must be presented in the release notes, make sure to add a changeset file. Check our guidelines for adding a changeset to your pull request: https://developer.rocket.chat/contribute-to-rocket.chat/modes-of-contribution/participate-in-rocket.chat-development/development-workflow#4.-adding-changeset-to-your-pull-request
21+
-->
22+
23+
## Issue(s)
24+
<!-- Link the issues being closed by or related to this PR. For example, you can use #333 if this PR closes issue number 333 -->
25+
26+
## Steps to test or reproduce
27+
<!-- Mention how you would reproduce the bug if not mentioned on the issue page already. -->

0 commit comments

Comments
 (0)