Thank you for your interest in the Redis.OM project - if you want to contribute we'd be positively delighted for you to get involved. Check out the sections below to see what you can do next.
If you encounter any issues while using Redis.OM please open an issue in GitHub. Issues should be opened if you find a bug in the Redis.OM software, an issue in the documentation, or if there's a neat new feature you'd like to see in Redis.OM. If you have any support/usage related questions those are best asked in Discord.
We welcome code contributions from the community, if you want to contribute code we ask the following:
- Open an issue, or have the code change directly related to an existing issue.
- Do not introduce any breaking changes to the Library without specific discussion in an underlying issue.
- The standard we use for a breaking change is if a developer would need to modify any code to upgrade, or if a developer would have to recompile their code to upgrade.
- Code changes should be relatively small and well described in the pull request.
- Code changes should be accompanied by tests that demonstrate coverage and regression for the issue.
- Fork this repo.
- Make your Code Changes.
- Write your tests.
- Use the
docker run -p 6379:6379 redis/redis-stack-server
as your local environment for running the functional tests. - Verify the tests pass (there may be a couple of deployment-specific tests (e.g. Sentinel/Cluster) in Redis.OM which will fail outside of the GH environment we've setup so don't worry about those).
- If it's your first time contributing please add your Github handle the the Contributors section in the README.
- Push your changes to GitHub.
- Open a PR.
We love updates to the docs, there's a couple places you can contribute to docs for this Library:
- The README here in GitHub is meant as a brief overview of the Redis.OM software
- The Redis Developer Github site has a fair amount of documentation about Redis.OM that we'd welcome contributions to.