Permalink
Browse files

Template for issues and pull-request

I've noticed that many issues are answered with "Please provide a jsfiddle".
This issue template tells the reporter to do that from the start.
1 parent 7535e48 commit 6c92579faff9d7ecdc0e74ee9a8e093780a0a20d @nknapp nknapp committed with nknapp Dec 2, 2016
Showing with 21 additions and 0 deletions.
  1. +10 −0 .github/ISSUE_TEMPLATE.md
  2. +11 −0 .github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,10 @@
+Before filing issues, please check the following points first:
+
+- [ ] Have a look at https://github.com/wycats/handlebars.js/blob/master/CONTRIBUTING.md
+- [ ] Read the FAQ at https://github.com/wycats/handlebars.js/blob/master/FAQ.md
+- [ ] Use the jsfiddle-template at https://jsfiddle.net/9D88g/47/ to reproduce problems or bugs
+
+This will probably help you to get a solution faster.
+For bugs, it would be great to have a PR with a failing test-case.
+
+
@@ -0,0 +1,11 @@
+Before creating a pull-request, please check https://github.com/wycats/handlebars.js/blob/master/CONTRIBUTING.md first.
+
+Generally we like to see pull requests that
+
+- [ ] Maintain the existing code style
+- [ ] Are focused on a single change (i.e. avoid large refactoring or style adjustments in untouched code if not the primary goal of the pull request)
+- [ ] Have good commit messages
+- [ ] Have tests
+- [ ] Don't significantly decrease the current code coverage (see coverage/lcov-report/index.html)
+
+

0 comments on commit 6c92579

Please sign in to comment.