]> git.madduck.net Git - etc/vim.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

CONTRIBUTING.md: add a section about issue reporting
authorSimon Ruggier <Simon80@gmail.com>
Sun, 24 May 2015 21:37:22 +0000 (17:37 -0400)
committerSimon Ruggier <Simon80@gmail.com>
Sun, 24 May 2015 21:38:11 +0000 (17:38 -0400)
CONTRIBUTING.md

index b29b8cc752ff828929801ea386f082b132355daf..a2c158087b5759bcdb1c039aa4b4d953676c08ca 100644 (file)
@@ -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!
+```