You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just in the same way as you build and upload the package to PyPI you could also set up a CI workflow that would upload to Anaconda Cloud (upon each release). I don't know if there is already a well-baked GitHub Action for that, but if not you could just specify the commands manually in the YAML yourself, setting your Anaconda username and passwd as repo secrets.
The only issue I can think of is that packages in anaconda usually contain all their dependencies...
So you would need to upload the MotEvo binary too...
Or you could hook it up to this package which would be a dependency.
This is sth to consider...
Just in the same way as you build and upload the package to
PyPI
you could also set up a CI workflow that would upload to Anaconda Cloud (upon each release). I don't know if there is already a well-baked GitHub Action for that, but if not you could just specify the commands manually in the YAML yourself, setting your Anaconda username and passwd as repo secrets.You may follow this tutorial: https://docs.conda.io/projects/conda-build/en/latest/user-guide/tutorials/build-pkgs.html
The only issue I can think of is that packages in anaconda usually contain all their dependencies...
So you would need to upload the MotEvo binary too...
Or you could hook it up to this package which would be a dependency.
This is sth to consider...
// Can be further automatized as in #7.
The text was updated successfully, but these errors were encountered: