-
Notifications
You must be signed in to change notification settings - Fork 9
add 'coverage' dev-dependency and update CONTRIBUTING.md #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -9,6 +9,7 @@ dependencies = ["agent-runtime", "memory-module", "litellm"] | |||
[tool.uv] | |||
package = false | |||
dev-dependencies = [ | |||
"coverage>=7.6.9", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if coverage details are that important at this stage of the project. But feel free to include it and have it run as a github action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with your point, but I think it's a good for two scenarios:
- setting up a quality bar for the team to enforce later on (I say later on because it's important for the team to move quickly now)
- people who aren't part of the core team can contribute via tests and learn the codebase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @stevengum, if you still have bandwidth, could you rebase this? We'd love to merge this in
Some failed tests? |
Example code coverage report in html format:
