bigbluebutton-Github/.github/PULL_REQUEST_TEMPLATE.md

<!--
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)
<!-- List here all the issues closed by this pull request. Use keyword `closes` before each issue number
Closes #123456
-->
Closes #

### Motivation
<!-- What inspired you to submit this pull request? -->


### How to test
<!-- List here everything that is necessary for the reviewer to be able to test it completely (docs link, step-by-step, bug cases)
- Is there any specific setup needed, different than the default?
- The linked issue contains all necessary content?
- Have you found any different case that might be tested when you were fixing/implementing it?
-->


### More
<!-- Anything else we should know when reviewing? -->
- [ ] Added/updated documentation
Create PULL_REQUEST_TEMPLATE.md 2020-05-26 09:05:30 +08:00			`<!--`
			`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. -->`

Update PULL_REQUEST_TEMPLATE.md 2024-09-18 21:41:14 +08:00
Create PULL_REQUEST_TEMPLATE.md 2020-05-26 09:05:30 +08:00			`### Closes Issue(s)`
Update PULL_REQUEST_TEMPLATE.md 2021-03-30 00:07:55 +08:00			<!-- List here all the issues closed by this pull request. Use keyword `closes` before each issue number
			`Closes #123456`
			`-->`
			`Closes #`
Create PULL_REQUEST_TEMPLATE.md 2020-05-26 09:05:30 +08:00
			`### Motivation`
			`<!-- What inspired you to submit this pull request? -->`


Update PULL_REQUEST_TEMPLATE.md 2024-09-18 21:41:14 +08:00			`### How to test`
			`<!-- List here everything that is necessary for the reviewer to be able to test it completely (docs link, step-by-step, bug cases)`
			`- Is there any specific setup needed, different than the default?`
			`- The linked issue contains all necessary content?`
			`- Have you found any different case that might be tested when you were fixing/implementing it?`
			`-->`


			`### More`
Create PULL_REQUEST_TEMPLATE.md 2020-05-26 09:05:30 +08:00			`<!-- Anything else we should know when reviewing? -->`
			`- [ ] Added/updated documentation`