-
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
Micromamba for ci #205
Micromamba for ci #205
Conversation
Thanks @Yun-Wu for your feedback in #179 (comment), which is relevant here too, is this is the same implementation. I have starting thinking through some alternate pathways in #207, but those will require more thought, so if its helpful to just use this PR's diff to unblock other work for now, please feel free to merge this (or not, if you are not blocked). |
environment-name: [ | ||
"py3.10-ecoscope1.8.2", | ||
"py3.11-ecoscope1.8.2", | ||
"py3.12-ecoscope1.8.2", | ||
] |
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.
Do we want to attach ecoscope version here? It means every time we upgrade ecoscope we need to change the github action too
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.
Synced offline and will resolve it later.
closes #206