Thanks for thinking about contributing to DeepEval! We accept fixes, improvements, or even entire new features. Some reasons why you might want to contribute:
Sign in to like and favorite skills
Thanks for thinking about contributing to DeepEval! We accept fixes, improvements, or even entire new features. Some reasons why you might want to contribute:
We follow fork and pull request workflow. To know more about it, check out this guide.
poetry install
To contribute, all we ask for is to follow existing patterns within the codebase. For example, if you're looking to add a new benchmark, look at how the different modules in the existing benchmarks are structured and implemented, and we encourage you to reuse helper functions and methods shared by similar modules.
Other than that, there are no strict rules to follow, except for optionally running
blackThank you and come ask any questions or discuss any new PRs you have in mind on our Discord!
Stale closure: We close issues with no activity for ≥ 12 months.
Reopening: If your issue is still relevant:
Exclusions: Labeled issues.
Why: Keeps the tracker actionable and reflects the current roadmap. If your issue still matters, please comment and we’ll re-open.