mirror of
https://codeberg.org/redict/redict.git
synced 2025-01-22 08:08:53 -05:00
5189838350
- Referring to Redis Discord channel instead of the mailing list. - Referring to the licensing instead of repeating it.
56 lines
2.4 KiB
Markdown
56 lines
2.4 KiB
Markdown
Note: by contributing code to the Redis project in any form, including sending
|
|
a pull request via GitHub, a code fragment or patch via private email or
|
|
public discussion groups, you agree to release your code under the terms
|
|
of the Redis license that you can find in the COPYING file included in the Redis
|
|
source distribution.
|
|
|
|
# IMPORTANT: HOW TO USE REDIS GITHUB ISSUES
|
|
|
|
GitHub issues SHOULD ONLY BE USED to report bugs and for DETAILED feature
|
|
requests. Everything else should be asked on Discord:
|
|
|
|
https://discord.com/invite/redis
|
|
|
|
PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected
|
|
bugs in the GitHub issues system. We'll be delighted to help you and provide
|
|
all the support on Discord.
|
|
|
|
There is also an active community of Redis users at Stack Overflow:
|
|
|
|
https://stackoverflow.com/questions/tagged/redis
|
|
|
|
Issues and pull requests for documentation belong on the redis-doc repo:
|
|
|
|
https://github.com/redis/redis-doc
|
|
|
|
If you are reporting a security bug or vulnerability, see SECURITY.md.
|
|
|
|
# How to provide a patch for a new feature
|
|
|
|
1. If it is a major feature or a semantical change, please don't start coding
|
|
straight away: if your feature is not a conceptual fit you'll lose a lot of
|
|
time writing the code without any reason. Start by posting in the mailing list
|
|
and creating an issue at Github with the description of, exactly, what you want
|
|
to accomplish and why. Use cases are important for features to be accepted.
|
|
Here you can see if there is consensus about your idea.
|
|
|
|
2. If in step 1 you get an acknowledgment from the project leaders, use the
|
|
following procedure to submit a patch:
|
|
|
|
a. Fork Redis on GitHub ( https://docs.github.com/en/github/getting-started-with-github/fork-a-repo )
|
|
b. Create a topic branch (git checkout -b my_branch)
|
|
c. Push to your branch (git push origin my_branch)
|
|
d. Initiate a pull request on GitHub ( https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request )
|
|
e. Done :)
|
|
|
|
3. Keep in mind that we are very overloaded, so issues and PRs sometimes wait
|
|
for a *very* long time. However this is not a lack of interest, as the project
|
|
gets more and more users, we find ourselves in a constant need to prioritize
|
|
certain issues/PRs over others. If you think your issue/PR is very important
|
|
try to popularize it, have other users commenting and sharing their point of
|
|
view, and so forth. This helps.
|
|
|
|
4. For minor fixes - open a pull request on GitHub.
|
|
|
|
Thanks!
|