# Contributing to Nexum

Thank you for considering contributing to Nexum! Your help is greatly appreciated.

## Reporting Issues

If you find any issues or bugs in Nexum, please open a GitHub issue. When reporting an issue, please provide the following details:

- A clear and descriptive title.
- A detailed description of the issue, including any error messages or logs.
- Steps to reproduce the issue.
- Your operating system and Rust version.

## Feature Requests

If you have a feature request or an idea for improving Nexum, please create a GitHub issue to discuss it. Describe the new feature or enhancement and how it could be useful.

## Pull Requests

We welcome contributions in the form of pull requests. If you'd like to contribute code or documentation, follow these steps:

1. Fork the repository.
2. Create a new branch for your feature or bug fix: `git checkout -b feature-name`.
3. Make your changes and commit them with a clear and concise message.
4. Push your branch to your fork: `git push origin feature-name`.
5. Create a pull request to the `main` branch of the Nexum repository.

Please ensure your pull request adheres to the following guidelines:

- Use clear and descriptive commit messages.
- Keep the code and documentation well-documented and up-to-date.
- Test your changes thoroughly.
- Ensure your code follows the existing coding style and formatting.

## Code of Conduct

Please review our [Code of Conduct](CODE_OF_CONDUCT.md) before contributing. We aim to create a welcoming and inclusive community for all contributors.

## License

By contributing to Nexum, you agree that your contributions will be licensed under the [MIT License](LICENSE).

Thank you for your interest in improving Nexum! Your contributions help make this library better for everyone.