tydids-core
Version:
A JavaScript library that empowers user defined Self-Sovereign Identity & Consent Management
35 lines (24 loc) • 2.58 kB
Markdown
## How to Contribute
There are several ways you can contribute to tydids-validation:
- **Bug Fixing** Identify and fix bugs in the existing codebase. You can find open issues labeled "bug" on the project's GitHub repository: https://github.com/energychain/tydids-validation
- **Feature Implementation** Contribute new features that align with the project's goals. Discuss potential features with the maintainers before starting development to avoid wasted effort.
- **Documentation Improvement** Help us improve the project's documentation by fixing errors, adding clarity, or providing additional examples.
- **Testing** Contribute new tests to ensure the project's functionality and robustness.
## Getting Started
Before contributing, we recommend the following steps:
- **Fork the Repository**: Create a fork of the tydids-validation repository on GitHub. This will allow you to make changes on your own copy before submitting them to the main project.
- **Set Up a Development Environment**: Follow the setup instructions in the project's README.md file to install dependencies and configure your development environment.
- **Review the Code Style**: Familiarize yourself with the project's coding style guide (if available) to maintain consistency.
- **Choose an Issue or Feature**: Look for existing issues to work on or discuss your proposed feature with the maintainers.
## Submitting a Pull Request
Once you've made your changes, follow these steps to submit a pull request:
- **Commit your Changes** Create meaningful commit messages that describe the changes you've made.
- **Push your Changes** Push your changes to your forked repository on GitHub.
- **Create a Pull Request** pen a pull request from your fork to the main branch of the tydids-validation repository.
- **Address Feedback** The maintainers may request changes or provide feedback on your pull request. Address these comments promptly to facilitate the review process.
## Additional Notes:
- **Testing** Ensure your changes include unit tests (if applicable) and pass all existing tests before submitting a pull request.
- **Code Style** Adhere to the project's coding style guidelines (if available) to maintain code consistency.
- **Licensing** All contributions must be submitted under the project's license (refer to the LICENSE.md file).
We appreciate your contributions!
This guide should help you get started with contributing to tydids-validation. If you have any questions, feel free to reach out to the maintainers through the GitHub repository or create an issue for discussion.