summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorPliable Pixels <pliablepixels@gmail.com>2016-11-22 12:38:35 -0400
committerPliable Pixels <pliablepixels@gmail.com>2016-11-22 12:38:35 -0400
commit4c4f0003bd44964e35d459203ac008a661aeb9f7 (patch)
tree677469971c3a55d2a73d2b07cfa9ba534aa06021 /CONTRIBUTING.md
parent716787db49898d528b41f43087400017a73a54c2 (diff)
nits
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8158b3a9..2ea2a93c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,7 +10,7 @@ Thanks.
It's best if you follow a proper process to contribute code - makes it easy for me to track/review. You will need `git`
If you are familiar with doing Pull Requests, you can ignore detailed instructions below - just do the following:
-* create a github issue in zmNinja describing your feature
+* create a [github issue](https://github.com/pliablepixels/zmNinja/issues) in zmNinja describing your feature
* create a fork and create a local branch using the issue# created (Example 459-new-feature)
* Make your changes on that branch and push/PR