First off, thank you for considering contributing to hyperlog-simd
. It's people like you that make hyperlog-simd
such a great tool. This document provides guidelines and steps for contributing.
While participating in this project, please follow our Code of Conduct.
- Use GitHub's issues. Open a new issue here.
- Use a clear and descriptive title for the issue to identify the problem.
- Provide as much relevant information as possible to reproduce the bug.
If you have an idea to improve or a new feature for hyperlog-simd
, we'd love to hear about it!
- Use GitHub's issues. Open a new issue here.
- Use a clear and descriptive title.
- Describe the current behavior and explain why it's insufficient.
- Describe the expected behavior.
Here's how to submit your contributions:
- Fork the repository 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.
- Address all review comments if the pull request receives any.
- Once approved, your pull request will be merged. Celebrate your success!
- Use the present tense ("Add feature" not "Added feature")
- Limit the first line to 72 characters or fewer
- Reference issues and pull requests in the description when appropriate
We follow the Rust community's best practices, including:
- Using
rustfmt
to ensure code adheres torustfmt
default settings. - Limiting lines to 100 characters.
- Commenting and documenting your code where necessary.
If you need help with the project:
- Ask a question on the issue you have or open a new issue.
- Reach out to the maintainers. (Make sure to respect the communication guidelines mentioned in the Code of Conduct)
Again, thanks for contributing! We appreciate your help in making hyperlog-simd
better. 🚀🦀