Support global .env at project level
allanbowe opened this issue · comments
When making auth operations in the CLI we have a project level .env file and also .env.targetname files - where the .env.targetname settings take precedence.
The VS Code extension should follow the same rules (look at .env.targetname first then .env for valid auth settings)
🎉 This issue has been resolved in version 1.25.0 🎉
The release is available on:
Your semantic-release bot 📦🚀