28 lines
1 KiB
Markdown
28 lines
1 KiB
Markdown
|
## Summary
|
||
|
|
|
||
|
|
Add a description of your merge request here. What does your new feature do?
|
||
|
|
|
||
|
|
Describe in detail what your patch does, why it does that, etc. Merge requests
|
||
|
|
without an adequate description are difficult to review, and probably we will
|
||
|
|
ask for more information!
|
||
|
|
|
||
|
|
Please also keep this description up-to-date with any discussion that takes
|
||
|
|
place so that reviewers can understand your intent. This is especially
|
||
|
|
important if they didn't participate in the discussion.
|
||
|
|
|
||
|
|
Make sure to remove this comment when you are done.
|
||
|
|
|
||
|
|
Implements <!-- GitLab Issue Number -->
|
||
|
|
|
||
|
|
## Test Plan
|
||
|
|
|
||
|
|
Add a description of how to test your patch here. Tell us how to use the new
|
||
|
|
feature and what we should be seeing. If applicable, it is great to include
|
||
|
|
screenshots, either here or in the Summary section.
|
||
|
|
|
||
|
|
It can be difficult to understand a new feature from the text description in
|
||
|
|
the summary, so put enough detail here that so that we can understand how to run
|
||
|
|
the new feature and we can play with it ourselves to understand it.
|
||
|
|
|
||
|
|
/label ~feature
|