We love your input! We want to make contributing to this project 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.
We Use GitHub Flow
All code changes happen through pull requests. We actively welcome your 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!
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using GitHub's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can
- 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)
- Clone the repository
- Run
bundle installto install dependencies - Run
bundle exec rake specto run tests - Make your changes
- Add tests for your changes
- Run
bundle exec rubocopto ensure code style - Create a pull request
# Run all tests
bundle exec rake spec
# Run with coverage
bundle exec rake coverage
# Run integration tests (requires Claude Code CLI)
bundle exec rake integration
# Run linter
bundle exec rubocopWe use RuboCop to maintain consistent code style. Please ensure your code passes RuboCop checks before submitting.
By contributing, you agree that your contributions will be licensed under its MIT License.
This document was adapted from the open-source contribution guidelines for Facebook's Draft