From 0cd5ea35e606f0c6f4208d211e552b6bec1acd18 Mon Sep 17 00:00:00 2001
From: Rich-Harris <richard.a.harris@gmail.com>
Date: Sun, 18 Sep 2016 13:30:42 -0400
Subject: [PATCH 1/2] add issue and pull request templates

---
 .github/ISSUE_TEMPLATE.md        | 18 ++++++++++++++++++
 .github/PULL_REQUEST_TEMPLATE.md |  8 ++++++++
 2 files changed, 26 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE.md
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000..8349819
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,18 @@
+<!--
+Thanks for raising an issue! To help us help you, if you've found a bug please consider the following:
+
+* If you can demonstrate the bug using the interactive [rollupjs.org](http://rollupjs.org) demo, please do.
+* If that's not possible, perhaps because your bug involves plugins, we recommend creating a small repo that illustrates the problem.
+
+Reproductions should be [small, self-contained, correct examples](http://sscce.org/). For example, if your bug isn't related to Gulp, **do not include Gulp in the repro**. (Side-note: if it *is* related to Gulp, this is the wrong issue tracker!) If possible, use a [config file](https://github.com/rollup/rollup/wiki/Command-Line-Interface#using-a-config-file) as it's the standard, favoured approach to using Rollup.
+
+Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that Rollup is run by unpaid volunteers in their free time, and we will prioritise bugs that follow these instructions.
+
+If you have a stack trace to include, we recommend putting inside a `<details>` block for the sake of the thread's readability:
+
+<details>
+  <summary>Stack trace</summary>
+
+  Stack trace goes here...
+</details>
+-->
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..6ff5a20
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,8 @@
+<!--
+Thank you for creating a pull request. Before submitting, please note the following:
+
+* If your pull request implements a new feature, please raise an issue to discuss it before sending code. In many cases features are absent for a reason.
+* This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
+* If necessary, and you know how, consider squashing your commits before merging. (This isn't essential but it keeps the history cleaner.)
+* Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to `npm run lint`!)
+-->

From 1a15b811185b2123b35d8edfb3a7a4c792733729 Mon Sep 17 00:00:00 2001
From: Rich-Harris <richard.a.harris@gmail.com>
Date: Sun, 18 Sep 2016 15:34:31 -0400
Subject: [PATCH 2/2] remove link markdown and squashing bullet point

---
 .github/ISSUE_TEMPLATE.md        | 4 ++--
 .github/PULL_REQUEST_TEMPLATE.md | 1 -
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 8349819..4e2b499 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -1,10 +1,10 @@
 <!--
 Thanks for raising an issue! To help us help you, if you've found a bug please consider the following:
 
-* If you can demonstrate the bug using the interactive [rollupjs.org](http://rollupjs.org) demo, please do.
+* If you can demonstrate the bug using the interactive http://rollupjs.org demo, please do.
 * If that's not possible, perhaps because your bug involves plugins, we recommend creating a small repo that illustrates the problem.
 
-Reproductions should be [small, self-contained, correct examples](http://sscce.org/). For example, if your bug isn't related to Gulp, **do not include Gulp in the repro**. (Side-note: if it *is* related to Gulp, this is the wrong issue tracker!) If possible, use a [config file](https://github.com/rollup/rollup/wiki/Command-Line-Interface#using-a-config-file) as it's the standard, favoured approach to using Rollup.
+Reproductions should be small, self-contained, correct examples – http://sscce.org. For example, if your bug isn't related to Gulp, **do not include Gulp in the repro**. (Side-note: if it *is* related to Gulp, this is the wrong issue tracker!) If possible, use a config file as it's the standard, favoured approach to using Rollup: https://github.com/rollup/rollup/wiki/Command-Line-Interface#using-a-config-file
 
 Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that Rollup is run by unpaid volunteers in their free time, and we will prioritise bugs that follow these instructions.
 
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 6ff5a20..d2882ac 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,6 +3,5 @@ Thank you for creating a pull request. Before submitting, please note the follow
 
 * If your pull request implements a new feature, please raise an issue to discuss it before sending code. In many cases features are absent for a reason.
 * This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
-* If necessary, and you know how, consider squashing your commits before merging. (This isn't essential but it keeps the history cleaner.)
 * Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to `npm run lint`!)
 -->