aboutsummaryrefslogtreecommitdiff
path: root/.gitlab
diff options
context:
space:
mode:
authorGaba <gaba@riseup.net>2020-12-22 09:05:55 -0300
committerAlexander Færøy <ahf@torproject.org>2021-02-12 18:36:42 +0000
commit3b0e0a87e77a120f3b18285ca223c33f83b8a5c7 (patch)
treeba04001e8bdf3412c4c091af899e047148cc5329 /.gitlab
parent71e9c56578e83e95e4ce622d0733b6f9bba3e11c (diff)
downloadtor-3b0e0a87e77a120f3b18285ca223c33f83b8a5c7.tar.gz
tor-3b0e0a87e77a120f3b18285ca223c33f83b8a5c7.zip
Adds issue creation templates for bugs, features, proposals and documentation.
Diffstat (limited to '.gitlab')
-rw-r--r--.gitlab/issue_templates/bug.md42
-rw-r--r--.gitlab/issue_templates/documentation.md35
-rw-r--r--.gitlab/issue_templates/feature.md15
-rw-r--r--.gitlab/issue_templates/proposal.md5
4 files changed, 97 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md
new file mode 100644
index 0000000000..d27dea552d
--- /dev/null
+++ b/.gitlab/issue_templates/bug.md
@@ -0,0 +1,42 @@
+<!--
+* Use this issue template for reporting a new bug.
+-->
+
+### Summary
+
+
+
+### Steps to reproduce:
+
+1. step 1
+2. step 2
+3. ...
+
+### What is the current bug behavior?
+
+
+
+### What is the expected behavior?
+
+
+
+### Environment
+
+<!--
+Please fill in the following information in bug reports, removing the comments like this one in brackets.
+-->
+
+- Version: e.g. 0.10, output of --version (without backslashes)
+- Operating system: Debian GNU/Linux 9.1 (stretch), Windows 7, Ubuntu Xenial, etc
+- Install method: distribution package, from source tarball, from git, etc
+- etc...
+
+### Relevant logs and/or screenshots:
+
+
+
+### Possible fixes:
+
+
+
+/label ~bug
diff --git a/.gitlab/issue_templates/documentation.md b/.gitlab/issue_templates/documentation.md
new file mode 100644
index 0000000000..6f0d4b49b8
--- /dev/null
+++ b/.gitlab/issue_templates/documentation.md
@@ -0,0 +1,35 @@
+<!--
+* Use this issue template for suggesting new docs or updates to existing docs.
+-->
+
+### Problem to solve
+
+<!-- Include the following detail as necessary:
+-->
+
+* What feature(s) affected?
+* What docs or doc section affected? Include links or paths.
+* Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
+* Any other ideas or requests?
+
+
+### Further details
+
+<!--
+* Include use cases, benefits, and/or goals for this work.
+* If adding content: What audience is it intended for? (What roles and scenarios?)
+-->
+
+### Proposal
+<!-- Further specifics for how can we solve the problem. -->
+
+
+### Who can address the issue
+<!-- What if any special expertise is required to resolve this issue? -->
+
+
+### Other links/references
+<!-- E.g. related Tor issues/MRs -->
+
+
+/label ~documentation
diff --git a/.gitlab/issue_templates/feature.md b/.gitlab/issue_templates/feature.md
new file mode 100644
index 0000000000..f0c3f1bdfe
--- /dev/null
+++ b/.gitlab/issue_templates/feature.md
@@ -0,0 +1,15 @@
+<!--
+* Use this issue template for submitting a feature.
+-->
+
+### Summary
+
+
+
+### What is the expected behavior?
+
+
+
+
+
+/label ~Feature
diff --git a/.gitlab/issue_templates/proposal.md b/.gitlab/issue_templates/proposal.md
new file mode 100644
index 0000000000..990ca70a0a
--- /dev/null
+++ b/.gitlab/issue_templates/proposal.md
@@ -0,0 +1,5 @@
+<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
+
+### Proposal
+
+<!-- Use this section to explain the proposal and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->