Dev: Update info in pull request template

LimeSurvey · Mar 12, 2020 · c7ec0ab · c7ec0ab · olleharstedt · Mar 12, 2020
1 parent ac4e0ac
commit c7ec0ab
Showing 1 changed file with 13 additions and 4 deletions.
diff --git a/docs/PULL_REQUEST_TEMPLATE b/docs/PULL_REQUEST_TEMPLATE
@@ -1,4 +1,13 @@
-Fixed issue # :
-New feature # :
-Changed feature # :
-Dev: 
+<!-- Thank you for contributing to LimeSurvey! To make our work easier, please make sure to follow the instructions below. Thank you. -->
+
+<!-- A pull request to LimeSurvey can either be a bug fix, a new feature or an internal development fix (refactoring etc). For bug fixes and new features, you must include the number to the Mantis ticket from bugs.limesurvey.org. For smaller internal changes, this is not necessary, but bigger refactoring tasks should always be discussed in a Mantis ticket before implementation and merge. -->
+
+<!-- Fixed issues should always go to the master branch, UNLESS they fix an issue in a yet unreleased feature in the develop branch. -->
+
+<!-- New features should always go to the develop branch. For more information about release schedule and code requirements, please see the following manual pages: https://manual.limesurvey.org/LimeSurvey_roadmap#Current_release_schedule and https://manual.limesurvey.org/How_to_contribute_new_features -->
+
+<!-- Keep one of the below lines. -->
+
+Fixed issue #<Mantis ticket number>:
+New feature #<Mantis ticket number>:
+Dev: