Python structure setup with new repo name#26
Merged
Conversation
10 tasks
Collaborator
Author
|
Hi @SarahAlidoost, I finished the rest of Python project setup tasks with the new repo name. Also ran the example notebook again and kept cell output. Can you give it a look? thanks! |
SarahAlidoost
requested changes
Feb 25, 2026
Member
There was a problem hiding this comment.
@rogerkuou thanks! looks very good 💯 Only one small suggestion on the readme and a comment about logo. Once the logo file is removed and the test are fixed, we can merge this.
Co-authored-by: SarahAlidoost <55081872+SarahAlidoost@users.noreply.github.com>
SarahAlidoost
approved these changes
Feb 26, 2026
Member
SarahAlidoost
left a comment
SarahAlidoost
left a comment
There was a problem hiding this comment.
@rogerkuou Thanks for addressing comments and fixing the action! 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix #6