diff options
| author | Pliable Pixels <pliablepixels@gmail.com> | 2016-11-22 12:35:54 -0400 |
|---|---|---|
| committer | Pliable Pixels <pliablepixels@gmail.com> | 2016-11-22 12:35:54 -0400 |
| commit | 148fcf21b5d03deabffc1e417a1683d0b34a2c5c (patch) | |
| tree | af7b8c6d78d08761fbae22d3606ca3ab711c00e0 | |
| parent | 3ec74aca8b718bf053a98e2c7d94b0335c6e82a5 (diff) | |
more details
| -rw-r--r-- | CONTRIBUTING.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7db18ba1..2ad29de7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,6 +9,13 @@ 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 fork and create a local branch using the issue# created (Example 459-new-feature) +* Make your changes on that branch and push/PR + +If you are not familiar with the Pull Request process, these steps explain further: + ### One time * [Fork](https://guides.github.com/activities/forking/) zmNinja using the "Fork" button on the top right of the [zmNinja project](https://github.com/pliablepixels/zmNinja). This creates your own copy (or fork) of zmNinja on github: |