Add issue templates

This commit adds issue templates for use in GitLab to hopefully improve
the quality of bug reports and feature requests that come in.

2 files changed, 62 insertions, 0 deletions

diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md
new file mode 100644
index 000000000..3c118a3cb
--- /dev/null
+++ b/.gitlab/issue_templates/Bug.md
@@ -0,0 +1,39 @@
+# Steps to reproduce
+<!--
+    Explain in detail what you were doing when the issue manifested.
+    If the issue affects only certain files, a sample would be appreciated.
+-->
+1.
+2.
+3.
+
+Reproducible in:
+<!--
+    To test, first install Flatpak following the steps in https://flatpak.org/getting.html.
+
+    Ubuntu users should perform these steps:
+        http://docs.flatpak.org/en/latest/using-flatpak.html#add-a-remote
+        http://docs.flatpak.org/en/latest/using-flatpak.html#install-applications (use the links below to install)
+
+    The stable version can be installed from https://flathub.org/repo/appstream/org.gnome.Nautilus.flatpakref.
+    The unstable version can be installed from https://git.gnome.org/browse/gnome-apps-nightly/plain/nautilus.flatpakref.
+
+    If these steps failed, write down the distribution you’re using and the version of Nautilus.
+-->
+* [ ] Flatpak stable
+* [ ] Flatpak unstable
+
+# Current behavior
+<!-- Describe the current (incorrect) behavior. -->
+
+# Expected behavior
+<!-- Describe the expected (correct) behavior. -->
+
+# Additional information
+<!--
+    If the issue is a crash, provide a stack trace following the steps in:
+    https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
+-->
+
+<!-- Ignore everything under this line. -->
+/label ~"1. Bug"
diff --git a/.gitlab/issue_templates/Feature.md b/.gitlab/issue_templates/Feature.md
new file mode 100644
index 000000000..87ea30b10
--- /dev/null
+++ b/.gitlab/issue_templates/Feature.md
@@ -0,0 +1,23 @@
+# Desired behavior
+<!-- In as much detail as possible, describe the functionality that you feel is missing. -->
+
+…
+
+# Use case
+<!-- Explain how the lack of this functionality affects your workflow. -->
+
+…
+
+<!-- Explain how the implementation of the functionality will improve your workflow. -->
+
+…
+
+# Possible drawbacks
+<!--
+    This is equally important; please consider how the feature could affect the project as a whole.
+    Do you believe that the average user will benefit from it? In other words, is it a niche use case?
+    By your estimations, would this incur a large technical debt to the developers?
+-->
+
+<!-- Ignore everything under this line. -->
+/label ~"1. Feature"