-
Notifications
You must be signed in to change notification settings - Fork 8
-
Notifications
You must be signed in to change notification settings - Fork 8
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
feature suggestion: export to .env change to import from .env #41
Comments
Guo-Zhang
changed the title
export to
feature suggestion: export to .env change to import from .env
Jun 17, 2021
Hi. Sorry, for some reason I missed this issue. Could you explain what issue is, since I'm not sure that I'm following? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is so confusing that this package support a feature as export to .env.
Where can we get the env variables locally or in cloud? It must be some common settings, like .env files or CI variables. It is unnecessary to export it, but I often need to import from a .env that is ignored by git and different in local env and cloud env.
With import feature, locally I can use .env file to export the env variables, and user CI env variables in CI pipelines.
The text was updated successfully, but these errors were encountered: