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
The README of conda-smithy now suggests that you should just set your channel in conda_build_config.yaml if you want to upload to a channel that is not conda-forge.
While this is true, the generated README still talks about conda-forge if you do that. To get the correct README you also have to set the channel in conda-forge.yaml. That's a bit unfortunate since it's redundant.
I don't know how all the conda_build_config.yaml files work. Is this intentional, i.e., could you have differing channels to push to? Then we should just document this redundancy better.
The README of conda-smithy now suggests that you should just set your channel in
conda_build_config.yaml
if you want to upload to a channel that is notconda-forge
.While this is true, the generated README still talks about
conda-forge
if you do that. To get the correct README you also have to set the channel inconda-forge.yaml
. That's a bit unfortunate since it's redundant.This is a followup to #991.
The text was updated successfully, but these errors were encountered: