Add Issue and Pull Request templates

Following https://help.github.com/articles/creating-an-issue-template-for-your-repository/

Adapted from:
 - https://github.com/harvesthq/chosen/blob/master/contributing.md
 - https://github.com/necolas/issue-guidelines
 - https://github.com/angular-translate/angular-translate/blob/master/ISSUE_TEMPLATE.md
 - https://raw.githubusercontent.com/Urigo/angular-meteor/master/.github/ISSUE_TEMPLATE.md

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,46 @@
+<!---
+Please read our [Contributing Guidelines](https://github.com/harvesthq/chosen/blob/master/contributing.md) before opening this bug report or feature request.
+
+Following these guidelines will help us get back to you more quickly, and will show that you care about making Chosen better just like we do!
+-->
+
+## Bug Report Template
+
+Describe your issue here.
+
+### My environment
+A summary of the issue and the browser/OS environment in which it occurs.
+
+### Steps to reproduce
+Tell us how to reproduce this issue.
+
+1. This is the first step
+2. This is the second step
+3. Further steps, etc.
+
+Please provide a working demo, you can use [this template](https://jsfiddle.net/hyktf3he) as a base.
+
+### Expected behaviour
+Tell us what should happen.
+
+### Actual behaviour
+Tell us what happens instead.
+
+### Additional information
+Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).
+
+See [here](https://github.com/harvesthq/chosen/blob/master/contributing.md#bug-reports) for more detail on what is expected of a feature request.
+
+---
+
+## Feature Request Template
+
+A description of the problem you're trying to solve, including *why* you think this is a problem, please add as much detail as possible.
+
+### Proposed Solution
+An overview of the suggested solution and why you believe this solution is appropriate.
+
+### Additional information
+Any other information you want to share that is relevant to the feature request. This might include proposed changes to the code, a breakdown of the problem or a mockup of how the new feature should look.
+
+See [here](https://github.com/harvesthq/chosen/blob/master/contributing.md#feature-requests) for more detail on what is expected of a feature request.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!---
+Good pull requests &mdash; patches, improvements, new features &mdash; are a fantastic help.
+They should remain focused in scope and avoid containing unrelated commits.
+
+Please follow our [code conventions](https://github.com/harvesthq/chosen/blob/master/contributing.md#code-conventions) before submitting your work. Adhering to these guidelines is the best way to get your work included in Chosen.
+-->
+
+## Pull Request Template
+
+Please provide: a clear title and description of the changes you've made, details of any issues these changes fix, why you believe this PR is suitable to be merged into chosen, and double check that:
+
+- [ ] All changes were made in CoffeeScript files, **not** JavaScript files.
+- [ ] You have used [Grunt](https://github.com/harvesthq/chosen/blob/master/contributing.md#grunt) to build the JavaScript files.
+- [ ] You've updated both the jQuery *and* Prototype versions
+- [ ] You haven't manually updated the version number in `package.json`.
+- [ ] If adding to, or adjusting, configuration; you've added, or updated, the [appropriate documentation](https://github.com/harvesthq/chosen/blob/master/public/options.html).
+
+See [here](https://github.com/harvesthq/chosen/blob/master/contributing.md#pull-requests) for more detail on what is expected of a pull request.