We love your input! We want to make contributing to GoRedis-Lite as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
# Clone your fork
git clone https://github.com/your-username/goredis-lite.git
cd goredis-lite
# Install dependencies
go mod download
# Run tests
make test
# Run linter
make lint
# Build the project
make build- Use
gofmtto format your code - Follow standard Go conventions
- Write clear commit messages
- Add comments for complex logic
- Write unit tests for new features
- Ensure all tests pass before submitting PR
- Include integration tests where appropriate
- Aim for good test coverage
We use GitHub issues to track public bugs. Report a bug by opening a new issue.
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
We actively welcome feature requests. Please use GitHub issues with the "enhancement" label.
By contributing, you agree that your contributions will be licensed under the MIT License.
This project adheres to a code of conduct. By participating, you are expected to uphold this code.