| 1 | # IMPORTANT: HOW TO USE REDIS GITHUB ISSUES |
| 2 | |
| 3 | * Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature |
| 4 | requests. Everything else belongs to the Redis Google Group. |
| 5 | |
| 6 | PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected |
| 7 | bugs in the Github issues system. We'll be very happy to help you and provide |
| 8 | all the support in the Redis Google Group. |
| 9 | |
| 10 | Redis Google Group address: |
| 11 | |
| 12 | https://groups.google.com/forum/?fromgroups#!forum/redis-db |
| 13 | |
| 14 | # How to provide a patch for a new feature |
| 15 | |
| 16 | 1. Drop a message to the Redis Google Group with a proposal of semantics/API. |
| 17 | |
| 18 | 2. If in steps 1 you get an acknowledge from the project leaders, use the |
| 19 | following procedure to submit a patch: |
| 20 | |
| 21 | a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) |
| 22 | b. Create a topic branch (git checkout -b my_branch) |
| 23 | c. Push to your branch (git push origin my_branch) |
| 24 | d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) |
| 25 | e. Done :) |
| 26 | |
| 27 | Thanks! |