From 368e8e302d7eb3f44e7875b4d880f68dd7cdd2fc Mon Sep 17 00:00:00 2001
From: Nicolas Coden <nicolas@ncoden.fr>
Date: Fri, 20 Apr 2018 22:39:39 +0200
Subject: [PATCH] chore: improve GitHub pull request template

This template was generated by https://www.talater.com/open-source-templates/#/ and modified according to our own CONTRIBUTION.md guidelines.
---
 .github/PULL_REQUEST_TEMPLATE.md | 40 ++++++++++++++++++++++++++++----
 1 file changed, 35 insertions(+), 5 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index d41473f05..b7e45ce31 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,8 +1,38 @@
-Before submitting a pull request, make sure it's targeting the right branch:
+<!--- Please fill the following template. Your pull request may be ignored otherwise. -->
 
-- For the latest version, use `develop`.
-- For bug fixes incompatible with `develop`, use the support branch of the latest compatible and supported version `support/6.x`.
+## Description
+<!--- Describe your changes in detail -->
 
-If you're fixing a JavaScript issue, it would help to create a new test case under the folder `test/visual/` that recreates the issue and show's that it's been fixed. Run `npm test` to compile the testing folder.
+<!--- This project only accepts pull requests related to open issues -->
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+<!--- If improving the documentation or fixing typo, you can ignore this -->
+- Closes <!--- link to issue... -->
 
-Happy coding! :)
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+
+## Screenshots (if appropriate):
+
+## Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Documentation
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+
+## Checklist (all required):
+<!--- Go over all the following points, and put an `x` in the boxes. All checkboxes are required! -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I have read the [CONTRIBUTING](CONTRIBUTING.md) document.
+- [ ] There is no other pull request similar to this one.
+- [ ] The pull request title is descriptive.
+- [ ] The template is fully and correctly filled.
+- [ ] The pull request target the right branch (`develop` or `support/*`).
+- [ ] My code follows the code style of this project.
+- [ ] I have updated the documentation accordingly to my changes (if relevant).
+- [ ] I have added tests to cover my changes (if relevant).
+- [ ] All new and existing tests passed.
+
+<!--- For more information, see the CONTRIBUTING.md document -->
+<!--- Thank you for your pull request and happy coding ;) -->
-- 
2.47.2