From c712fe357b92dcc794a9b9360b338bcb79bfd542 Mon Sep 17 00:00:00 2001
From: Dan Dascalescu <ddascalescu+github@gmail.com>
Date: Wed, 8 Jan 2025 07:15:50 +0200
Subject: [PATCH] --env-file looks in parent directories

---
 runtime/reference/env_variables.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/runtime/reference/env_variables.md b/runtime/reference/env_variables.md
index bdefcc5dc..1b59e4d12 100644
--- a/runtime/reference/env_variables.md
+++ b/runtime/reference/env_variables.md
@@ -27,7 +27,8 @@ console.log(Deno.env.has("FIREBASE_AUTH_DOMAIN")); // true
 
 Deno supports `.env` files. You can cause Deno to read environment variables
 from `.env` using the `--env-file` flag: `deno run --env-file <script>`. This
-will read `.env` by default; if you want or need to load environment variables
+will read `.env` from the current working directory or the first parent
+directory that contains one; if you want to load environment variables
 from a different file, you can specify that file as a parameter to the flag.
 Additionally, you can pass multiple `--env-file` flags (e.g.,
 `deno run --env-file=.env.one --env-file=.env.two --allow-env <script>`) to load