blob: 02769a0f84707278ed65b805dea2dbbf808457f7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
<!-- remove all unused parts
The title of your PR should be descriptive and concise. It should be in the format of `Type: Description`. For example, `Feature: Add new command` or `Fix: Bug in command`. If there are multiple types of changes these can be separated by a plus. For example, `Feature + Fix: Add new command and fix bug in command`.
## PR Reviews
When your PR is marked as ready for review, some of our maintainers will look through your code to make sure everything is good to go. In order to do this, they may request some changes you will need to do, **or fix smaller stuff (like merge conflicts) for you**. If a maintainer has reviewed your PR, make sure to **pull any of their changes** into your local project before doing more work on your code. Having maintainers fix small stuff for you helps us speed up the process of merging your PR, so if some of your systems warrant further care, be sure to let us know (preferably with a code comment).
Make sure to only mark your PR as "Ready to review" when it is. If you still want to do major changes, you can keep a draft PR open until then.
-->
## Dependencies
- pr_number_or_link_here
## What
Describe what this pull request does, including technical details, screenshots, links to discord, etc.
<details>
<summary>Images</summary>
<!-- drop images here -->
</details>
## Changelog New Features
+ Cool new feature. - your_name_here
* Extra info.
## Changelog Improvements
+ Improved cool feature. - your_name_here
* Extra info.
## Changelog Fixes
+ Fixed cool feature. - your_name_here
* Extra info.
## Changelog Technical Details
+ Something technical you changed in the backend. - your_name_here
* Extra info.
## Changelog Removed Features
+ Removed cool feature. - your_name_here
* Extra info.
|
