Skip to content
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

The environment name on "environment-file" is not defined, using "enviroment-activate"! #104

Closed
tdegeus opened this issue Nov 18, 2020 · 2 comments

Comments

@tdegeus
Copy link

tdegeus commented Nov 18, 2020

How should I deal with this warning:

The environment name on "environment-file" is not defined, using "enviroment-activate"!

FYI:

    - name: Set conda environment "test"
      uses: conda-incubator/setup-miniconda@v2
      with:
        mamba-version: "*"
        channels: conda-forge,defaults
        channel-priority: true
        environment-file: environment.yaml
        activate-environment: test
        auto-activate-base: false

A second question is if I should modify to get rid of

Warning: 'defaults' already in 'channels' list, moving to the top
@goanpeca
Copy link
Member

Hi @tdegeus, thanks for the report

The action "prefers" that environment yaml files include a name section, so in case it is not existent, or it is different to test or it does not match with what is specified on acitvate-environment then we raise that warning. There is no "fixing"to do from your side, except add the name: key.

The second warning is something that needs fixing, and is tracked on #57

They are both warnings so they are harmless :) .

@tdegeus
Copy link
Author

tdegeus commented Nov 19, 2020

Thank @goanpeca , very clear, thanks!

@tdegeus tdegeus closed this as completed Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants