35 lines
1.0 KiB
Markdown
35 lines
1.0 KiB
Markdown
<!--
|
|
PLEASE READ THIS MESSAGE.
|
|
|
|
HOW TO WRITE A GOOD PULL REQUEST?
|
|
|
|
- Make it small.
|
|
- Do only one thing.
|
|
- Avoid re-formatting.
|
|
- Make sure the code builds and works.
|
|
- Write useful descriptions and titles.
|
|
- Address review comments in terms of additional commits.
|
|
- Do not amend/squash existing ones unless the PR is trivial.
|
|
- Read the contributing guide: https://docs.bigbluebutton.org/support/faq.html#bigbluebutton-development-process
|
|
- Sign and send the Contributor License Agreement: https://docs.bigbluebutton.org/support/faq.html#why-do-i-need-to-sign-a-contributor-license-agreement-to-contribute-source-code
|
|
|
|
-->
|
|
|
|
### What does this PR do?
|
|
|
|
<!-- A brief description of each change being made with this pull request. -->
|
|
|
|
### Closes Issue(s)
|
|
|
|
closes #...
|
|
<!-- List here all the issues closed by this pull request. Use keyword `closes` before each issue number -->
|
|
|
|
### Motivation
|
|
|
|
<!-- What inspired you to submit this pull request? -->
|
|
|
|
### More
|
|
|
|
<!-- Anything else we should know when reviewing? -->
|
|
- [ ] Added/updated documentation
|