| Q             | A
| ------------- | ---
| Branch?       | master <!--see comment below-->
| Bug fix?      | yes/no
| New feature?  | yes/no
| BC breaks?    | yes/no
| Deprecations? | yes/no
| Tests pass?   | yes/no
| Fixed tickets | #... <!-- #-prefixed issue number(s), if any -->
| License       | MPL-v2.0

<!--
- Bug fixes must be submitted against the lowest branch where they apply
  (lowest branches are regularly merged to upper ones so they get the fixes too).
- Features and deprecations must be submitted against the master branch.
- Please fill in this template according to the PR you're about to submit.
- Replace this comment by a description of what your PR is solving.
-->

| Q             | A
| ------------- | ---
| Bug fix?      | yes/no
| New feature?  | yes/no   <!-- don't forget to update src/**/CHANGELOG.md files -->
| BC breaks?    | no       <!-- see http://docs.park-manager.com/en/latest/contributing/code/bc.html -->
| Deprecations? | yes/no   <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tests pass?   | yes      <!-- please add some, will be required by reviewers -->
| Fixed tickets | #...     <!-- #-prefixed issue number(s), if any -->
| License       | MPL-v2.0

<!--
Write a short README entry for your feature/bugfix here (replace this comment block.)
This will help people understand your PR and can be used as a start of the Doc PR.
Additionally:
  Pull request must be submitted against the master branch, maintainers 
  may cherry-pick commits to lower branches is applyable.
-->

Remove branch requirements from pr-template
doc: Remove branch requirements from pr-template

All pull requests must target the master branch now
