Permalink
Browse files

remove link markdown and squashing bullet point

  • Loading branch information...
1 parent 0cd5ea3 commit 1a15b811185b2123b35d8edfb3a7a4c792733729 @Rich-Harris Rich-Harris committed Sep 18, 2016
Showing with 2 additions and 3 deletions.
  1. +2 −2 .github/ISSUE_TEMPLATE.md
  2. +0 −1 .github/PULL_REQUEST_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 exampleshttp://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.
@@ -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`!)
-->

0 comments on commit 1a15b81

Please sign in to comment.