Contribution

We welcome and appreciate all contributions to REN.Kit! Whether you’re fixing a bug, adding a new feature, improving documentation, or suggesting a better architecture, your input helps us build a better toolkit for the whole .NET community.

How to Contribute

  1. Fork the Repository Start by forking the REN.Kit repository to your own GitHub account.

  2. Create a Branch Create a new branch for your change, based on the main branch (or latest release branch if specified).

    git checkout -b my-feature-or-bugfix

  3. Make Your Changes Implement your feature, bug fix, or documentation improvements. Please try to follow the existing code style and best practices.

  4. Test Your Changes Add or update unit tests to cover your changes. Make sure that all existing and new tests pass.

  5. Submit a Pull Request Push your branch and open a Pull Request (PR) against the main repository. Describe your changes and reference any related issues if applicable.

  6. Collaborate on Review The project maintainers will review your PR. Be ready to discuss feedback and iterate if needed!

Contribution Guidelines

  • Please open an issue first if you want to discuss a new feature or major refactor before starting development.

  • Follow the naming conventions and coding standards used in the project.

  • Keep PRs focused—one change per PR is ideal.

  • Include documentation and example usage if your contribution affects public APIs.

Code of Conduct

We’re committed to fostering a welcoming and inclusive environment. Please be respectful and constructive in all interactions.

Questions or Help?

If you’re unsure where to start or need help with something, open an issue or join the discussion! Every contribution—big or small—matters.

Thank you for helping make REN.Kit.DataKit better!

PreviousGetting StartedNextMigration Guide

Last updated