From 80fdb213d83f1cb22461ab67e60363505d8a8fcb Mon Sep 17 00:00:00 2001
From: Davide Bortolami <d@fermiumlabs.com>
Date: Sun, 29 Mar 2020 22:34:39 +0100
Subject: [PATCH] Add PR template, issue templates

---
 .github/ISSUE_TEMPLATE/bug_report.md          | 34 +++++++++++++++++++
 .github/ISSUE_TEMPLATE/feature_request.md     | 23 +++++++++++++
 .../question-about-using-frappe_docker.md     | 12 +++++++
 .github/PULL_REQUEST_TEMPLATE.md              |  7 ++++
 4 files changed, 76 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md
 create mode 100644 .github/ISSUE_TEMPLATE/question-about-using-frappe_docker.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..d4c7a8c1
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Report a bug encountered while using the Frappe_docker
+labels: bug
+---
+
+<!--
+Welcome to the frappe_docker issue tracker! Before creating an issue, please heed the following:
+
+1. Is your issue relevant to the frappe_docker or the main Frappe framework? https://github.com/frappe/frappe . if It's the latter, publish the issue there.
+2. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
+3. When making a bug report, make sure you provide all the required information. The easier it is for maintainers to reproduce, the faster it'll be fixed.
+4. If you think you know what the reason for the bug is, share it with us. Maybe put in a PR 😉
+-->
+
+## Description of the issue
+
+## Context information (for bug reports)
+
+## Steps to reproduce the issue
+
+1.
+2.
+3.
+
+### Observed result
+
+### Expected result
+
+### Stacktrace / full error message if available
+
+```
+(paste here)
+```
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 00000000..15c410eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea to improve frappe_docker
+labels: enhancement
+---
+
+<!--
+Welcome to the Frappe Framework issue tracker! Before creating an issue, please heed the following:
+1. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
+2. When making a feature request, make sure to be as verbose as possible. The better you convey your message, the greater the drive to make it happen.
+-->
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/question-about-using-frappe_docker.md b/.github/ISSUE_TEMPLATE/question-about-using-frappe_docker.md
new file mode 100644
index 00000000..02fdd694
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/question-about-using-frappe_docker.md
@@ -0,0 +1,12 @@
+---
+name: Question about using Frappe/Frappe Apps
+about: Ask how to do something
+labels: question
+---
+
+<!--
+Welcome to the frappe_docker issue tracker! Before creating an issue, please heed the following:
+
+1. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
+2. Please write extensively, clearly and in detail.
+-->
\ No newline at end of file
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..6c9fc532
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,7 @@
+> Please provide enough information so that others can review your pull request:
+
+<!-- You can skip this if you're fixing a typo or updating existing documentation -->
+
+> Explain the **details** for making this change. What existing problem does the pull request solve?
+
+<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->