Evan Van Dam

Results 32 issues of Evan Van Dam

Hi @joho, I noticed some unexpected behavior when using `godotenv` from the command line. When passing multiple .env files, if one listed first does not exist, it looks like it...

Hey @joho I was just wondering if it was possible to have an ARM release for this project? It would be great to just install it with curl in environments...

We're using [secrets-init](https://github.com/doitintl/secrets-init) in combination with [godotenv](https://github.com/joho/godotenv) to source environment variables and then inject secrets into the environment. We're seeing unexpected behavior where secrets-init does not set environment variables properly...

#### Description It seems like the first few environment variables documented for the VCS prompt element don't have the `_VCS` included. I only tested setting `POWERLEVEL9K_VCS_HIDE_BRANCH_ICON`, but would assume the...

### Behaviour Hey folks, similar to https://github.com/docker/metadata-action/issues/191 a bit, when running a workflow on a PR event, the `{{ sha }}` refers to the temporary merge commit to the target...

investigate

Hey @alexei-led thanks for the project. I noticed confusing behavior that secrets-init doesn't set an environment variable if it already exists as an empty value. Can this behavior be changed...

We're using [secrets-init](https://github.com/doitintl/secrets-init) in combination with [godotenv](https://github.com/joho/godotenv) to source environment variables and then inject secrets into the environment. We're seeing unexpected behavior where secrets-init does not set environment variables properly...

Hey @alexei-led Thanks for the project, it's really helpful! I was wondering if it's possible to have an option/flag to exit non-zero if a secret can't be found/accessed instead of...

I typically open `~/terraform` in VS Code, which has multiple root modules, ex: ``` ├── configs │   ├── dev │   │   ├── global │   │   └── us-west-2 │   ├── prod...

Hey @nickstenning thanks for this project! I was wondering if there's a way to prevent a .env file from overwriting an existing env var. Consider the following example: ```shell $...