[tor-commits] [community/staging] Add description templates for gitlab

[hiro at torproject.org]

commit d182313a0feacc44309e57b1db77dd51abed9c3c
Author: Pili Guerra <pili at piliguerra.com>
Date:   Tue Jun 4 15:12:21 2019 +0200

    Add description templates for gitlab
---
 .gitlab/issue_templates/Bug.md     | 45 ++++++++++++++++++++++++++++++++++++++
 .gitlab/issue_templates/Feature.md | 24 ++++++++++++++++++++
 2 files changed, 69 insertions(+)

diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md
new file mode 100644
index 0000000..7f702f8
--- /dev/null
+++ b/.gitlab/issue_templates/Bug.md
@@ -0,0 +1,45 @@
+<!---
+Please read this!
+
+Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "regression" or "bug" label.
+
+For the Community Edition issue tracker:
+
+- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression
+- https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug
+
+For the Enterprise Edition issue tracker:
+
+- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression
+- https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug
+
+and verify the issue you're about to submit isn't a duplicate.
+--->
+
+### Summary
+
+(Summarize the bug encountered concisely)
+
+### Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+### What is the current *bug* behavior?
+
+(What actually happens)
+
+### What is the expected *correct* behavior?
+
+(What you should see instead)
+
+### Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
+
+
+### Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~bug
\ No newline at end of file
diff --git a/.gitlab/issue_templates/Feature.md b/.gitlab/issue_templates/Feature.md
new file mode 100644
index 0000000..24aedbb
--- /dev/null
+++ b/.gitlab/issue_templates/Feature.md
@@ -0,0 +1,24 @@
+### Problem to solve
+
+<!-- What problem do we solve? -->
+
+### Intended users
+
+<!-- Who will use this feature? -->
+
+### Further details
+
+<!-- Include use cases, benefits, and/or goals -->
+
+### Proposal
+
+<!-- How are we going to solve the problem? -->
+
+
+### What does success look like, and how can we measure that?
+
+<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
+
+### Links / references
+
+/label ~feature
\ No newline at end of file