Skip to content

feature suggestion: export to .env change to import from .env #41

@Guo-Zhang

Description

@Guo-Zhang

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions