Thank you for your interest in contributing to json-test! This document provides guidelines and information about contributing to this project.
Please file bug reports on the GitHub issue tracker. When filing a bug report, please include:
- A clear description of the problem
- Minimal steps to reproduce the issue
- What you expected to happen
- What actually happened
- Version of json-test you're using
Feature requests are welcome! Please submit them on the issue tracker and:
- Describe the feature you'd like to see
- Explain why this feature would be useful
- Be aware that features should fit within the scope of the library
We appreciate pull requests! To contribute code:
- Fork the repository and create a new branch
- Write your changes, including tests
- Update documentation as needed
- Ensure all tests pass with
cargo test
- Submit a pull request
- Add tests for any new functionality
- Update documentation as needed
- Clearly describe your changes in the PR description
- Write relevant tests for all new functionality
- Ensure existing tests pass
- Include both positive and negative test cases
- Test edge cases
- Update documentation for any changed functionality
- Include examples in documentation
- Keep documentation clear and concise
- Check that documentation builds without warnings
The maintainers will handle releases. The process includes:
- Updating version numbers
- Updating CHANGELOG.md
- Creating git tags
- Publishing to crates.io
If you need help with your contribution:
- Open a GitHub issue with your question
- Tag it with "question" or "help wanted"
- Be patient and respectful
Thank you for contributing to json-test!