Add pull request and issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,14 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is. Please explain what you observe and what you expected to happen instead. If there is an exception, include its message and stack trace.
+
+**To Reproduce**
+Try to add the steps needed to reproduce the problem. Feel free to open a pull request with a failing test if that makes sense. Otherwise, at least provide some code and / or YAML that reproduce the issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,10 @@
+---
+name: Question
+about: For general usage questions
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+Feel free to ask any question on how to use the library. Alternatively, consider asking the question on [Stackoverflow](https://stackoverflow.com), tagged with [yamldotnet](https://stackoverflow.com/questions/tagged/yamldotnet).

.github/pull_request_template.md

@@ -0,0 +1,18 @@
+## Welcome!
+
+Thanks for your interest in contributing to this project. Any contribution will
+be gladly accepted, provided that they are generally useful and follow the
+conventions of the project.
+
+1. Please create **one pull request for each feature**. This results in smaller pull requests that are easier to review and validate.
+
+1. **Avoid reformatting existing code** unless you are making other changes to it.  
+   - Cleaning-up of `using`s is acceptable, if you made other changes to that file.
+   - If you believe that some code is badly formatted and needs fixing, isolate that change in a separate pull request.
+
+1. Always add one or more **unit tests** that prove that the feature / fix you are submitting is working correctly.
+
+1. Please **describe the motivation** behind the pull request. Explain what was the problem / requirement. Unless the implementation is self-explanatory, also describe the solution.
+   * Of course, there's no need to be too verbose. Usually one or two lines will be enough.
+
+1. Follow the project's [coding conventions](CONTRIBUTING.md#coding-style)

CONTRIBUTING.md

@@ -14,8 +14,8 @@ All contributions should be submitted as pull requests.
 1. Please create **one pull request for each feature**. This results in smaller pull requests that are easier to review and validate.
 
 1. **Avoid reformatting existing code** unless you are making other changes to it.
-  * Cleaning-up of `using`s is acceptable, if you made other changes to that file.
-  * If you believe that some code is badly formatted and needs fixing, isolate that change in a separate pull request.
+   * Cleaning-up of `using`s is acceptable, if you made other changes to that file.
+   * If you believe that some code is badly formatted and needs fixing, isolate that change in a separate pull request.
 
 1. Always add one or more **unit tests** that prove that the feature / fix you are submitting is working correctly.