From 3858ad729b6e06eb2fd2b3180c8c4fb8c0edc75b Mon Sep 17 00:00:00 2001
From: Aaron <aaron@sajatypeworks.com>
Date: Tue, 19 Nov 2019 09:40:57 -0800
Subject: [PATCH] Adding .github folder

---
 .github/ISSUE_TEMPLATE/Bug_Report.md          | 51 +++++++++++++++++++
 .github/ISSUE_TEMPLATE/Documentation_Issue.md | 10 ++++
 .github/ISSUE_TEMPLATE/Feature_Request.md     | 34 +++++++++++++
 .github/PULL_REQUEST_TEMPLATE.md              | 22 ++++++++
 4 files changed, 117 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/Bug_Report.md
 create mode 100644 .github/ISSUE_TEMPLATE/Documentation_Issue.md
 create mode 100644 .github/ISSUE_TEMPLATE/Feature_Request.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 000000000..44b8b111d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/Bug_Report.md
@@ -0,0 +1,51 @@
+---
+name: Bug report 🐛
+about: Report errors or unexpected behavior
+title: "Bug Report (IF I DO NOT CHANGE THIS THE ISSUE WILL BE CLOSED)"
+labels: ''
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+<!--
+This bug tracker is monitored by Windows Terminal development team and other technical folks.
+
+Please use this form and describe your issue, concisely but precisely, with as much detail as possible including images.
+
+-->
+
+# Environment
+
+```none
+Cascadia Code version number:
+Application (with version) used to display text:
+OS platform and version:
+Screen resolution (i.e. 220dpi): 
+
+Any other software?
+```
+
+# Steps to reproduce
+
+<!-- A description of how to trigger this bug. -->
+
+# Expected behavior
+
+<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
+
+# Actual behavior
+
+<!-- What's actually happening? -->
diff --git a/.github/ISSUE_TEMPLATE/Documentation_Issue.md b/.github/ISSUE_TEMPLATE/Documentation_Issue.md
new file mode 100644
index 000000000..f4b08497c
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/Documentation_Issue.md
@@ -0,0 +1,10 @@
+---
+name: Documentation Issue 📚
+about: Report issues in our documentation
+title: "Documentation Issue"
+labels: Issue-Docs
+assignees: ''
+
+---
+
+<!-- Briefly describe which document needs to be corrected and why. -->
diff --git a/.github/ISSUE_TEMPLATE/Feature_Request.md b/.github/ISSUE_TEMPLATE/Feature_Request.md
new file mode 100644
index 000000000..c4978769a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/Feature_Request.md
@@ -0,0 +1,34 @@
+---
+name: Feature Request/Idea 🚀
+about: Suggest a new feature or improvement (this does not mean you have to implement it)
+title: "Feature Request"
+labels: Issue-Feature
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+# Description of the new feature/enhancement (with images if possible)
+
+<!-- 
+A clear and concise description of what the problem is that the new feature would solve.
+Describe why and how a user would use this new functionality (if applicable).
+-->
+
+# Proposed technical implementation details (optional)
+
+<!-- 
+A clear and concise description of what you want to happen.
+-->
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..205bf76a0
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,22 @@
+<!-- Enter a brief description/summary of your PR here. What character(s) are you changing/creating and how was it tested (even manually, if necessary)? Did you hint the entire font or only the modified character(s)? -->
+## Summary of the Pull Request
+
+<!-- Other than the issue solved, is this relevant to any other issues/existing PRs? --> 
+## References
+
+<!-- Please review the items on the PR checklist before submitting-->
+## PR Checklist
+* [ ] Closes #xxx
+* [ ] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA
+* [ ] Requires FONTLOG.txt to be updated
+* [ ] Requires [/images/cascadia-code.png](/microsoft/cascadia-code/blob/master/images/cascadia-code.png) and/or [/images/cascadia-code-characters.png](/microsoft/cascadia-code/blob/master/images/cascadia-code-characters.png) to be updated
+* [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx
+
+<!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here -->
+## Detailed Description of the Pull Request / Additional comments
+
+<!-- Provide images of the character(s) that are being modified/created at different screen sizes. Clearly identifying specific code points is heavily recommended. -->
+## Before (if applicable) and After Images of the Character(s)
+
+<!-- Describe how you validated the behavior. List steps that were taken. -->
+## Validation Steps Performed
\ No newline at end of file