Closed michalbundyra closed 5 years ago
Configuation is completely revamped for version 2.0.0. If a token is specified for the requested provider within the global configuration, it will be used — unless you specify a different one via the --provider-token
option.
Tokens are no longer allowed in local configuration, as it is too easy to check it in to your repository by accident, and file permissions are not secure.
I have created global configuration with token. I was expected that it will be used on release, but I have to do it manually and I think the message is not clear that I can use global configuration.
What I would suggest is to have fallback to global configuration if there is no local configuration or at least change the error message to suggest maybe using global configuration if provided. Now we have: