fdiblen / anaconda-action Goto Github PK

Hi! Many thanks for making this action available.
I copied the code in the Example usage section of the README but when I run the workflow I got the following warning:

Warning: Unexpected input(s) 'envFileName', valid inputs are ['entryPoint', 'args', 'env-name', 'env-file-name', 'python-version', 'channels', 'activate-env', 'publish', 'publish-channel', 'anaconda-token']

It seems to be a change in the naming convention, but I'm confused since I did not specified the other key-value pairs appearing under with: which are:

env-name: environment.yml
env-file-name: environment.yml
python-version: default
activate-env: true
publish: false

(I only copied the example code as is in the README)

Finally, I understand Anaconda-Action step is completing successfully and my workflow is failing in run unit tests step.

@fdiblen Faruk man, long time, bro, hope you doing good! We - myself and @bouweandela - would like to get the conda build and upload to the esmvalgroup channel done automatically when we release a new version so Bouwe suggested your GA workflow. Currently I implemented a GA workflow that does the conda package build (see here) so was wondering how we can integrate your workflow in it - particularily, where is the bit that does the anaconda login. Could you have a look and give me some pointers when you gots some time pls, dude? 🍺