Add templates for bug and feature issues as well as PRs.

.github/ISSUE_TEMPLATE/BUG.md

@@ -0,0 +1,92 @@
+---
+name: Bug report
+about: Report a problem with rest-server to help us resolve it and improve
+---
+
+
+<!--
+Welcome! - We kindly ask that you:
+
+  1. Fill out the issue template below - not doing so needs a good reason.
+  2. Use the forum if you have a question rather than a bug or feature request.
+
+The forum is at: https://forum.restic.net
+
+NOTE: Not filling out the issue template needs a good reason, as otherwise it
+may take a lot longer to find the problem, not to mention it can take up a lot
+more time which can otherwise be spent on development. Please also take the
+time to help us debug the issue by collecting relevant information, even if
+it doesn't seem to be relevant to you. Thanks!
+
+The forum is a better place for questions about rest-server or general suggestions
+and topics, e.g. usage or documentation questions! This issue tracker is mainly
+for tracking bugs and feature requests directly relating to the development of
+the software itself, rather than the project.
+
+Thanks for understanding, and for contributing to the project!
+-->
+
+
+Output of `rest-server --version`
+---------------------------------
+
+
+How did you run rest-server exactly?
+------------------------------------
+
+<!--
+This section should include at least:
+
+ * The complete command line and any environment variables you used to
+   configure rest-server's backend access. Make sure to replace sensitive values!
+
+ * The output of the commands, what rest-server prints gives may give us much
+   information to diagnose the problem!
+-->
+
+
+What backend/server/service did you use to store the repository?
+----------------------------------------------------------------
+
+
+Expected behavior
+-----------------
+
+<!--
+Describe what you'd like rest-server to do differently.
+-->
+
+
+Actual behavior
+---------------
+
+<!--
+Please try to concentrate on observations, so only describe what you observed directly.
+-->
+
+
+Steps to reproduce the behavior
+-------------------------------
+
+<!--
+The more time you spend describing an easy way to reproduce the behavior (if
+this is possible), the easier it is for the project developers to fix it!
+-->
+
+
+Do you have any idea what may have caused this?
+-----------------------------------------------
+
+
+Do you have an idea how to solve the issue?
+-------------------------------------------
+
+
+Did rest-server help you today? Did it make you happy in any way?
+-----------------------------------------------------------------
+
+<!--
+Answering this question is not required, but if you have anything positive to share, please do so here!
+Sometimes we get tired of reading bug reports all day and a little positive end note does wonders.
+Idea by Joey Hess, https://joeyh.name/blog/entry/two_holiday_stories/
+-->

.github/ISSUE_TEMPLATE/FEATURE.md

@@ -0,0 +1,58 @@
+---
+name: Feature request/enhancement
+about: Suggest a new feature or enhancement for rest-server
+---
+
+
+<!--
+Welcome! - We kindly ask that you:
+
+  1. Fill out the issue template below - not doing so needs a good reason.
+  2. Use the forum if you have a question rather than a bug or feature request.
+
+The forum is at: https://forum.restic.net
+
+The forum is a better place for questions about rest-server or general suggestions
+and topics, e.g. usage or documentation questions! This issue tracker is mainly
+for tracking bugs and feature requests directly relating to the development of
+the software itself, rather than the project.
+
+Thanks for understanding, and for contributing to the project!
+-->
+
+
+Output of `rest-server --version`
+---------------------------------
+
+<!--
+Please add the version of rest-server you're currently using here, this helps us
+later to see what has changed in rest-server when we revisit this issue after some
+time.
+-->
+
+
+What should rest-server do differently?
+---------------------------------------
+
+<!--
+Please describe the feature you'd like to see added or changed here.
+-->
+
+
+What are you trying to do? What is your use case?
+-------------------------------------------------
+
+<!--
+This section should contain a brief description what you're trying to do, which
+would be possible after implementing the new feature.
+-->
+
+
+Did rest-server help you today? Did it make you happy in any way?
+-----------------------------------------------------------------
+
+<!--
+Answering this question is not required, but if you have anything positive to share, please do so here!
+Sometimes we get tired of reading bug reports all day and a little positive end note does wonders.
+Idea by Joey Hess, https://joeyh.name/blog/entry/two_holiday_stories/
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+<!--
+Thank you very much for contributing code or documentation to rest-server!
+Please fill out the following questions to make it easier for us to review
+your changes.
+
+You do not need to check all the boxes below all at once, feel free to take
+your time and add more commits. If you're done and ready for review, please
+check the last box.
+-->
+
+
+What is the purpose of this change? What does it change?
+--------------------------------------------------------
+
+<!--
+Describe the changes here, as detailed as needed.
+-->
+
+
+Was the change discussed in an issue or in the forum before?
+------------------------------------------------------------
+
+<!--
+Link issues and relevant forum posts here.
+
+If this PR resolves an issue on GitHub, write "Closes #1234" such
+that the issue is closed automatically when this PR is merged.
+-->
+
+
+Checklist
+---------
+
+- [ ] I have added tests for all changes in this PR
+- [ ] I have added documentation for the changes (in the manual)
+- [ ] There's a new file in `changelog/unreleased/` that describes the changes for our users (template [here](https://github.com/restic/rest-server/blob/master/changelog/TEMPLATE))
+- [ ] I have run `gofmt` on the code in all commits
+- [ ] All commit messages are formatted in the same style as [the other commits in the repo](https://github.com/restic/rest-server/commits/master)
+- [ ] I'm done, this Pull Request is ready for review