-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix for # 100 - Remove model library and access #130
Conversation
Thanks @bahadzie, I'll take a look today. Could you close and re-open the PR to trigger the required workflows, and maybe also fix the merge conflict? |
Hi @bahadzie, thanks for the PR - could you rebase it on |
e93389a
to
b863f25
Compare
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.
Thanks for this PR @bahadzie - I only have a few comments which I've left on the files. Just FYI I've rebased this on main
, and another rebase would probably be necessary soon as I'm merging #128.
For future reference @amanda-minter had asked about where users might be able to find information on the models, including the compartment names, so I do think the model library is something we should reconsider in future; perhaps once there are more models.
Just a note on the last commit 9e55bee - we try to rebase on main so as not to have these update commits. Once checks pass, I'll squash-merge this PR rather than rebasing; more on Epiverse merge strategy here in the Blueprints. |
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.
Thanks for fixing @bahadzie, looks good to me and squash-merging this now.
No description provided.