Why is BINSTAR_TOKEN handled differently than all other token?

[jankatins]

I'm currently trying to build a multiple recipe version of conda-smithy and found that all access token go into a subdir of ~, but only the BINSTAR_TOKEN is requested to be in os.environ. Is it ok, to change that to also use a file based access token ( ~\.conda-smithy\anaconda.token)?

[pelson]

Is it ok, to change that to also use a file based access token ( ~.conda-smithy\anaconda.token)?

Sure. Makes sense to me 👍

[pelson]

This was done. Thanks @JanSchulz

[jankatins]

Seems this commit was not applied: the binstar token is still gotten from the environment and not from anaconda.token https://github.com/conda-forge/conda-smithy/blob/master/conda_smithy/ci_register.py#L36

Commits are here: jankatins@8f73d00 and maybe 36dfa1a

Should I port these commits to the current codebase? The first commit is now in #177