First, thanks for wanting to contribute. You’re awesome! ❤️
We’re not able to provide support through GitHub Issues. If you’re looking for help with your code, try posting on Stack Overflow.
All features should be documented. If you don’t see a feature in the docs, assume it doesn’t exist.
Think you’ve discovered a bug?
- Search existing issues to see if it’s been reported.
- Try the
masterbranch to make sure it hasn’t been fixed.
gem "searchkick", github: "ankane/searchkick"- Try the
debugoption when searching. This can reveal useful info.
Product.search("something", debug: true)If the above steps don’t help, create an issue.
- Recreate the problem by forking this gist. Include a link to your gist and the output in the issue.
- For exceptions, include the complete backtrace.
If you’d like to discuss a new feature, create an issue and start the title with [Idea].
Fork the project and create a pull request. A few tips:
- Keep changes to a minimum. If you have multiple features or fixes, submit multiple pull requests.
- Follow the existing style. The code should read like it’s written by a single person.
- Add one or more tests if possible. Make sure existing tests pass with:
bundle exec rake testFeel free to open an issue to get feedback on your idea before spending too much time on it.
This contributing guide is released under CCO (public domain). Use it for your own project without attribution.