From af5bd7c119e061838d483fb9903f456e09e73518 Mon Sep 17 00:00:00 2001 From: Simon Ruggier Date: Sun, 24 May 2015 17:37:22 -0400 Subject: [PATCH] CONTRIBUTING.md: add a section about issue reporting --- CONTRIBUTING.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b29b8cc7..a2c15808 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -37,3 +37,18 @@ If you wish to have a behavior that differs from that style guide, add an option # Tests All new features must have unit tests. + +# Issues + +Issues are tracked within GitHub. + +When reporting issues, your report is more effective if you include a minimal example file that reproduces the problem. Try to trim out as much as possible, until you have the smallest possible file that still reproduces the issue. Paste the example inline into your issue report, quoted using four spaces at the beginning of each line, like this example from issue [#189](https://github.com/plasticboy/vim-markdown/issues/189): + +``` +Minimal example: + + ``` + = + ``` + bad! +```