virtualx-engine/.github/PULL_REQUEST_TEMPLATE.md

<!--
Please target the `master` branch in priority.
PRs can target `3.x` if the same change was done in `master`, or is not relevant there.

Relevant fixes are cherry-picked for stable branches as needed by maintainers.
You can mention in the description if the change is compatible with `3.x`.

To speed up the contribution process and avoid CI errors, please set up pre-commit hooks locally:
https://docs.godotengine.org/en/latest/contributing/development/code_style_guidelines.html
-->
Add a PR template with a message about PRs needing to be for master [ci skip] Co-authored-by: Rémi Verschelde <rverschelde@gmail.com> 2020-07-22 19:04:47 +02:00			`<!--`
Rewrite PR template to make it slightly less verbose 2022-06-28 16:10:54 +02:00			Please target the `master` branch in priority.
			PRs can target `3.x` if the same change was done in `master`, or is not relevant there.
Add a PR template with a message about PRs needing to be for master [ci skip] Co-authored-by: Rémi Verschelde <rverschelde@gmail.com> 2020-07-22 19:04:47 +02:00
Rewrite PR template to make it slightly less verbose 2022-06-28 16:10:54 +02:00			`Relevant fixes are cherry-picked for stable branches as needed by maintainers.`
			You can mention in the description if the change is compatible with `3.x`.
Link to Code style guidelines in the pull request template This is a common pain point for new contributors, as setting up pre-commit hooks will save a lot of time spent on CI. 2023-06-15 07:19:44 +02:00
			`To speed up the contribution process and avoid CI errors, please set up pre-commit hooks locally:`
			`https://docs.godotengine.org/en/latest/contributing/development/code_style_guidelines.html`
Add a PR template with a message about PRs needing to be for master [ci skip] Co-authored-by: Rémi Verschelde <rverschelde@gmail.com> 2020-07-22 19:04:47 +02:00			`-->`