-
Notifications
You must be signed in to change notification settings - Fork 404
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
Enhance Logging for Code Repository Interactions in ZenML #2256
Comments
Hi, this issue seems interesting, and I would like to contribute. Although the link to code repositories seems broken (this one). Also could you share some additional docs to get started with the work? |
@og118 Thanks for helping out! Currently , the docs arent the best ones, so please feel free to ask here in this issue as you progress. But the two relevant sections are: https://docs.zenml.io/user-guide/production-guide/connect-code-repository https://docs.zenml.io/user-guide/advanced-guide/configuring-zenml/connect-your-git-repository |
Hello I ca either take up this issue or issue number #2253, both are unassigned |
@AryaMoghaddam more than welcome! |
Open Source Contributors Welcomed!
Please comment below if you would like to work on this issue!
Contact Details [Optional]
[email protected]
What happened?
Users currently do not receive sufficient feedback from ZenML regarding the status and actions taken when interacting with code repositories. Specifically, there is a lack of clear log messages in scenarios where the pipeline code in a repository is dirty/has unpushed changes, or when previously built Docker images cannot be reused due to certain repository conditions.
Task Description
Improve the logging mechanism in ZenML to provide additional and clearer log messages that explain the reasoning behind certain actions or inactions when using code repositories. This includes informing users about the need to commit and push changes for reusing previously built Docker images, and explaining why builds are or are not being reused.
Expected Outcome
Steps to Implement
Additional Context
Effective communication and feedback when interacting with code repositories are crucial for a seamless user experience in ZenML, especially for users managing complex pipelines with dependencies on repository states.
Code of Conduct
The text was updated successfully, but these errors were encountered: