Contributing to RepoDB

RepoDB started as a simple idea: give .NET developers a data access library that is fast, honest about what it's doing, and free — forever. That ORM is now the foundation of something bigger: a full productivity ecosystem for data access, spanning bulk operations, telemetry, and multi-database support, all built in the open by the community that uses it.

None of that happens without contributors. RepoDB has no corporate sponsor bankrolling a full-time team — it succeeds because developers like you show up: fixing a bug you hit in production, writing the doc page you wished existed, adding the provider your stack needs, or just telling us where it broke. Every contribution, big or small, moves the whole .NET data ecosystem forward and helps keep a genuinely free, high-performance alternative alive for everyone who relies on it.

Your contribution matters — not just to RepoDB, but to every team that depends on it being fast, correct, and free.

✅ Ways to Contribute

You don't need to be a core maintainer or a database expert to make an impact. Pick whatever fits your time and skills:

• Write code. Browse issues labeled for grabs — these are curated as good entry points — and submit a pull request. See Issuing a Pull Request and our Coding Standards to get started smoothly.
• Report a bug. Hit something unexpected? File an issue — see Reporting an Issue for what makes a report actionable. Precise bug reports are one of the highest-leverage contributions there is.
• Propose an idea. Have a feature or improvement in mind? Open an issue to start the discussion before you write code — it saves everyone rework and often leads to a better design.
• Improve the docs. Clear documentation is what turns a good library into an adopted one. Contribute to the documentation site — fix a typo, clarify an example, or write the guide you wish you'd had.
• Help others. Answer questions on StackOverflow or in the Microsoft Teams community. Community support is a force multiplier — it scales far beyond what any small maintainer team can do alone.
• Spread the word. Blog about RepoDB, share it with your team, or simply give the repo a :star:. Visibility brings in the next wave of contributors and keeps the project healthy long-term.

✅ Before You Start

• Check existing issues and open pull requests to avoid duplicating work.
• For non-trivial changes, open an issue first to align on approach before investing significant time.
• Review Building the Solutions to get your local environment running.
• Keep an eye on Limitations and the Support Policy so your contribution lands where it's most useful.

✅ Recognition

Every contributor is listed in our contributors graph, and we mean that as more than a formality — this project is built by its community, and we want that to be visible to everyone who benefits from it.

Thank you for helping keep RepoDB fast, free, and open for the entire .NET community.