init

stevemao · Mar 2, 2016 · 4d80905c7e0f680d6fa0638795d5ac0129455dc7 · 4d80905
commit 4d80905c7e0f680d6fa0638795d5ac0129455dc7
diff --git a/bugs-only/ISSUE_TEMPLATE.md b/bugs-only/ISSUE_TEMPLATE.md
@@ -0,0 +1,32 @@
+  
+Issue tracker is **ONLY** used for reporting bugs. NO NEW FEATURE ACCEPTED! Use [stackoverflow](https://stackoverflow.com) for supporting issues.
+  
+
+  
+<!--- Provide a general summary of the issue in the Title above -->
+  
+
+  
+## Expected Behavior
+  
+<!--- Tell us what should happen -->
+  
+
+  
+## Current Behavior
+  
+<!--- Tell us what happens instead of the expected behavior -->
+  
+
+  
+## Possible Solution
+  
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+  
+
+  
+## Steps to Reproduce
+  
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+  
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+  
+1.
+  
+2.
+  
+3.
+  
+4.
+  
+
+  
+## Context (Environment)
+  
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+  
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+  
+
+  
+<!--- Provide a general summary of the issue in the Title above -->
+  
+
+  
+## Detailed Description
+  
+<!--- Provide a detailed description of the change or addition you are proposing -->
+  
+
+  
+## Possible Implementation
+  
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->
diff --git a/bugs-only/PULL_REQUEST_TEMPLATE.md b/bugs-only/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,23 @@
+  
+Bug Fixes **ONLY**. NO NEW FEATURE ACCEPTED!
+  
+
+  
+<!--- Provide a general summary of your changes in the Title above -->
+  
+
+  
+## Description
+  
+<!--- Describe your changes in detail -->
+  
+
+  
+## Related Issue
+  
+<!--- This project only accepts pull requests related to open issues -->
+  
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+  
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+  
+<!--- Please link to the issue here: -->
+  
+
+  
+## Motivation and Context
+  
+<!--- Why is this change required? What problem does it solve? -->
+  
+<!--- If it fixes an open issue, please link to the issue here. -->
+  
+
+  
+## How Has This Been Tested?
+  
+<!--- Please describe in detail how you tested your changes. -->
+  
+<!--- Include details of your testing environment, and the tests you ran to -->
+  
+<!--- see how your change affects other areas of the code, etc. -->
+  
+
+  
+## Screenshots (if appropriate):
diff --git a/checklist/ISSUE_TEMPLATE.md b/checklist/ISSUE_TEMPLATE.md
@@ -0,0 +1,17 @@
+  
+# Please follow the general troubleshooting steps first:
+  
+
+  
+- [ ] Ran ?
+  
+- [ ] Ran ?
+  
+- [ ] If you're seeing permission errors ?
+  
+
+  
+<!-- You can erase any parts of this template not applicable to your Issue. -->
+  
+
+  
+### Bug reports:
+  
+
+  
+Please replace this line with a brief summary of your issue **AND** if reporting a build issue include the link from:
+  
+
+  
+### Features:
+  
+
+  
+**Please note by far the quickest way to get a new feature is to file a Pull Request.**
+  
+
+  
+We will consider your request but it may be closed if it's something we're not actively planning to work on.
diff --git a/checklist/PULL_REQUEST_TEMPLATE.md b/checklist/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,17 @@
+  
+### All Submissions:
+  
+
+  
+* [ ] Have you followed the guidelines in our Contributing document?
+  
+* [ ] Have you checked to ensure there aren't other open [Pull Requests](../../pulls) for the same update/change?
+  
+
+  
+<!-- You can erase any parts of this template not applicable to your Pull Request. -->
+  
+
+  
+### New Feature Submissions:
+  
+
+  
+1. [ ] Does your submission pass tests?
+  
+2. [ ] Have you lint your code locally prior to submission?
+  
+
+  
+### Changes to Core Features:
+  
+
+  
+* [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
+  
+* [ ] Have you written new tests for your core changes, as applicable?
+  
+* [ ] Have you successfully ran tests with your changes locally?
diff --git a/checklist2/ISSUE_TEMPLATE.md b/checklist2/ISSUE_TEMPLATE.md
@@ -0,0 +1,28 @@
+  
+### Prerequisites
+  
+
+  
+* [ ] Can you reproduce the problem in safe mode?
+  
+* [ ] Are you running the latest version?
+  
+* [ ] Did you check the debugging guide?
+  
+* [ ] Did you check the FAQs on Discuss?
+  
+* [ ] Are you reporting to the correct repository?
+  
+* [ ] Did you perform a cursory search?
+  
+
+  
+For more information, see the `CONTRIBUTING` guide.
+  
+
+  
+### Description
+  
+
+  
+[Description of the bug or feature]
+  
+
+  
+### Steps to Reproduce
+  
+
+  
+1. [First Step]
+  
+2. [Second Step]
+  
+3. [and so on...]
+  
+
+  
+**Expected behavior:** [What you expected to happen]
+  
+
+  
+**Actual behavior:** [What actually happened]
+  
+
+  
+### Versions
+  
+
+  
+You can get this information from executing `npm version`.
diff --git a/checklist2/PULL_REQUEST_TEMPLATE.md b/checklist2/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,11 @@
+  
+## Types of changes
+  
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+  
+- [ ] Bug fix (non-breaking change which fixes an issue)
+  
+- [ ] New feature (non-breaking change which adds functionality)
+  
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+  
+- [ ] I have read the **CONTRIBUTING** document.
+  
+- [ ] My code follows the code style of this project.
+  
+- [ ] My change requires a change to the documentation.
+  
+- [ ] I have updated the documentation accordingly.
+  
+- [ ] I have added tests to cover my changes.
+  
+- [ ] All new and existing tests passed.
diff --git a/conversational/ISSUE_TEMPLATE.md b/conversational/ISSUE_TEMPLATE.md
@@ -0,0 +1,38 @@
+  
+**Note: for support questions, please use stackoverflow**. This repository's issues are reserved for feature requests and bug reports.
+  
+
+  
+* **I'm submitting a ... **
+  
+[ ] bug report
+  
+[ ] feature request
+  
+[ ] support request => Please do not submit support request here, see note at the top of this template.
+  
+
+  
+
+  
+* **Do you want to request a *feature* or report a *bug*?**
+  
+
+  
+
+  
+
+  
+* **What is the current behavior?**
+  
+
+  
+
+  
+
+  
+* **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem** via
+  
+https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
+  
+
+  
+
+  
+
+  
+* **What is the expected behavior?**
+  
+
+  
+
+  
+
+  
+* **What is the motivation / use case for changing the behavior?**
+  
+
+  
+
+  
+
+  
+* **Please tell us about your environment:**
+  
+
+  
+- version: 2.0.0-beta.X
+  
+- Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
+  
+- Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart]
+  
+
+  
+
+  
+
+  
+* **Other information** (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
diff --git a/conversational/PULL_REQUEST_TEMPLATE.md b/conversational/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,23 @@
+  
+* **Please check if the PR fulfills these requirements**
+  
+- [ ] The commit message follows our guidelines
+  
+- [ ] Tests for the changes have been added (for bug fixes / features)
+  
+- [ ] Docs have been added / updated (for bug fixes / features)
+  
+
+  
+
+  
+* **What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
+  
+
+  
+
+  
+
+  
+* **What is the current behavior?** (You can also link to an open issue here)
+  
+
+  
+
+  
+
+  
+* **What is the new behavior (if this is a feature change)?**
+  
+
+  
+
+  
+
+  
+* **Does this PR introduce a breaking change?** (What changes might users need to make in their application due to this PR?)
+  
+
+  
+
+  
+
+  
+* **Other information**:
diff --git a/must-open-issue-before-pr/ISSUE_TEMPLATE.md b/must-open-issue-before-pr/ISSUE_TEMPLATE.md
@@ -0,0 +1,21 @@
+  
+Hey there and thank you for using Issue Tracker!
+  
+
+  
+Our project, as you've probably heard, is getting really popular and truth is we're getting a bit overwhelmed by the activity surrounding it. There are just too many issues for us to manage properly.
+  
+
+  
+Do the checklist before filing an issue:
+  
+
+  
+- [ ] Is this something you can **debug and fix**? Send a pull request! Bug fixes and documentation fixes are welcome.
+  
+- [ ] Have a usage question? Ask your question on [StackOverflow](http://stackoverflow.com). We use StackOverflow for usage question and GitHub for bugs.
+  
+- [ ] Have an idea for a feature? Post the feature request on Product Pains. It has a voting system to surface the important issues. GitHub issues should only be used for bugs.
+  
+
+  
+
+  
+None of the above, create a bug report
+  
+------------------------------------------------------------------
+  
+
+  
+Make sure to add **all the information needed to understand the bug** so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.
+  
+
+  
+- [ ] Provide a **minimal code snippet** / [rnplay](https://rnplay.org/) example that reproduces the bug.
+  
+- [ ] Provide **screenshots** where appropriate
+  
+- [ ] What's the **version** of React Native you're using?
+  
+- [ ] Does this occur on iOS, Android or both?
+  
+- [ ] Are you using Mac, Linux or Windows?
diff --git a/must-open-issue-before-pr/PULL_REQUEST_TEMPLATE.md b/must-open-issue-before-pr/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,25 @@
+  
+Please do not create a Pull Request without creating an issue first.
+  
+Any change needs to be discussed before proceeding.
+  
+Failure to do so may result in the rejection of the pull request.
+  
+
+  
+Please provide enough information so that others can review your pull request:
+  
+
+  
+<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
+  
+
+  
+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. -->
+  
+
+  
+**Test plan (required)**
+  
+
+  
+Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
+  
+
+  
+<!-- Make sure tests pass on both Travis and Circle CI. -->
+  
+
+  
+**Code formatting**
+  
+
+  
+<!-- See the simple style guide. -->
+  
+
+  
+**Closing issues**
+  
+
+  
+Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
diff --git a/no-duplicates/ISSUE_TEMPLATE.md b/no-duplicates/ISSUE_TEMPLATE.md
@@ -0,0 +1,33 @@
+  
+Your issue may already be reported!
+  
+Please search on the [issue track](../) before creating one.
+  
+
+  
+## Expected Behavior
+  
+<!--- If you're describing a bug, tell us what should happen -->
+  
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+  
+
+  
+## Current Behavior
+  
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+  
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+  
+
+  
+## Possible Solution
+  
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+  
+<!--- or ideas how to implement the addition or change -->
+  
+
+  
+## Steps to Reproduce (for bugs)
+  
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+  
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+  
+1.
+  
+2.
+  
+3.
+  
+4.
+  
+
+  
+## Context
+  
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+  
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+  
+
+  
+## Your Environment
+  
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+  
+* Version used:
+  
+* Browser Name and version:
+  
+* Operating System and version (desktop or mobile):
+  
+* Link to your project:
diff --git a/no-duplicates/PULL_REQUEST_TEMPLATE.md b/no-duplicates/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,40 @@
+  
+A similar PR may already be submitted!
+  
+Please search among the [Pull request](../) before creating one.
+  
+
+  
+Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
+  
+
+  
+For more information, see the `CONTRIBUTING` guide.
+  
+
+  
+
+  
+**Summary**
+  
+
+  
+<!-- Summary of the PR -->
+  
+
+  
+This PR fixes/implements the following **bugs/features**
+  
+
+  
+* [ ] Bug 1
+  
+* [ ] Bug 2
+  
+* [ ] Feature 1
+  
+* [ ] Feature 2
+  
+* [ ] Breaking changes
+  
+
+  
+<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
+  
+
+  
+Explain the **motivation** 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. -->
+  
+
+  
+**Test plan (required)**
+  
+
+  
+Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
+  
+
+  
+<!-- Make sure tests pass on both Travis and Circle CI. -->
+  
+
+  
+**Code formatting**
+  
+
+  
+<!-- See the simple style guide. -->
+  
+
+  
+**Closing issues**
+  
+
+  
+<!-- Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
+  
+Fixes #
diff --git a/questions-answers/ISSUE_TEMPLATE.md b/questions-answers/ISSUE_TEMPLATE.md
@@ -0,0 +1,22 @@
+  
+## *Who* is the bug affecting?
+  
+<!-- Ex. All supervisors, Sally Supervisor, Level 1 CCs -->
+  
+
+  
+## *What* is affected by this bug?
+  
+<!-- Ex. supervision, sending messages, texter profiles -->
+  
+
+  
+## *When* does this occur?
+  
+<!-- Ex. After ending a conversation, every night at 3pm, when I sign off -->
+  
+
+  
+## *Where* on the platform does it happen?
+  
+<!-- Ex. In the a Supervisor chat box, on the conversation profile page, on the two-factor screen -->
+  
+
+  
+
+  
+## *How* do we replicate the issue?
+  
+<!-- Please be specific as possible. Use dashes (-) or numbers (1.) to create a list of steps -->
+  
+
+  
+
+  
+## Expected behavior (i.e. solution)
+  
+<!-- What should have happened? -->
+  
+
+  
+
+  
+##Other Comments
diff --git a/questions-answers/PULL_REQUEST_TEMPLATE.md b/questions-answers/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,28 @@
+  
+<!--- Provide a general summary of your changes in the Title above -->
+  
+
+  
+## Description
+  
+<!--- Describe your changes in detail -->
+  
+
+  
+## Motivation and Context
+  
+<!--- Why is this change required? What problem does it solve? -->
+  
+<!--- If it fixes an open issue, please link to the issue here. -->
+  
+
+  
+## How Has This Been Tested?
+  
+<!--- Please describe in detail how you tested your changes. -->
+  
+<!--- Include details of your testing environment, tests ran to see how -->
+  
+<!--- your change affects other areas of the code, etc. -->
+  
+
+  
+## Screenshots (if appropriate):
+  
+
+  
+## Types of changes
+  
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+  
+- [ ] Bug fix (non-breaking change which fixes an issue)
+  
+- [ ] New feature (non-breaking change which adds functionality)
+  
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+  
+
+  
+## Checklist:
+  
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+  
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+  
+- [ ] My code follows the code style of this project.
+  
+- [ ] My change requires a change to the documentation.
+  
+- [ ] I have updated the documentation accordingly.
diff --git a/readme.md b/readme.md
@@ -0,0 +1,11 @@
+  
+# GitHub issue templates
+  
+
+  
+> A collection of GitHub issue and pull request templates
+  
+
+  
+GitHub finally supports [issue template](https://github.com/blog/2111-issue-and-pull-request-templates).
+  
+
+  
+# 10+ templates for you to pick!
+  
+
+  
+Find your issue/PR templates, and just grab and go.
+  
+
+  
+Inspired by Excellent GitHub projects.
diff --git a/screenshots/ISSUE_TEMPLATE.md b/screenshots/ISSUE_TEMPLATE.md
@@ -0,0 +1,13 @@
+  
+### Issue and Steps to Reproduce
+  
+<!-- Describe your issue and tell us how to reproduce it (include any useful information). -->
+  
+
+  
+### Versions
+  
+
+  
+### Screenshots
+  
+
+  
+#### Expected
+  
+
+  
+#### Actual
+  
+
+  
+### Additional Details
+  
+* Installed packages: