Add issue templates for bugs and feature requests

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

.gitlab/issue_templates/Bug.md

@@ -0,0 +1,31 @@
+## Summary
+
+<!--
+Summarize the bug encountered concisely. See
+https://wayland.freedesktop.org/libinput/doc/latest/reporting-bugs.html for
+detailed instructions to report bugs
+-->
+
+## Steps to reproduce
+
+<!-- How one can reproduce the issue - this is very important -->
+
+## libinput version you encountered the bug on
+
+<!-- Note: if your libinput version is older than the current stable version,
+please reproduce with a current version instead -->
+
+## Hardware information:
+
+<!-- Model name/number and general hardware information if applicable -->
+
+## Other log output:
+
+- `libinput record` output: <!-- attach file here -->
+- `libinput debug-events --verbose` output: <!-- attach file here -->
+
+<!-- Paste any other relevant logs - please use code blocks (```) to format
+console output, logs, and code as it's very hard to read otherwise.) -->
+
+
+/label ~bug ~needs-investigation

.gitlab/issue_templates/FeatureRequest.md

@@ -0,0 +1,32 @@
+<!--
+
+Before your file a feature request, please read
+
+https://wayland.freedesktop.org/libinput/doc/latest/what-is-libinput.html
+
+The amount of developer time libinput has available is very small.
+Requesting a feature is no guarantee that it will get implemented. Someone
+(you!) needs to step up to do the work.
+
+-->
+
+## Summary
+
+<!-- Summarize the requested feature in a few sentences.  -->
+
+## Feature details
+
+<!-- A step-by-step list of what the feature should achieve (where applicable) -->
+
+## Affected Hardware
+
+<!-- Which hardware types would be affected by this -->
+
+## Implementation in Other Systems
+
+<!-- Does this feature already exist elsewhere? How does it work there? Try
+to provide as many details as possible -->
+
+
+
+/label ~RFE ~needs-investigation