From ef7cf86c6ed01bf7d9cac8379bdc4bb0ece4c905 Mon Sep 17 00:00:00 2001
From: Volodymyr Radchenko <30495731+rreckonerr@users.noreply.github.com>
Date: Wed, 30 Jun 2021 17:53:15 +0300
Subject: [PATCH] DOC: `--no-override` flag should be set for `env-cmd` example

By default `env-cmd` WILL override the globally defined env vars, which differs from the default `dotenv` behavior and adds confusion.

Refs: #11162
---
 docusaurus/docs/deployment.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docusaurus/docs/deployment.md b/docusaurus/docs/deployment.md
index 85f4a7d09f0..11c509d9f16 100644
--- a/docusaurus/docs/deployment.md
+++ b/docusaurus/docs/deployment.md
@@ -151,7 +151,7 @@ For example, to create a build environment for a staging environment:
    ```json
    {
      "scripts": {
-       "build:staging": "env-cmd -f .env.staging npm run build"
+       "build:staging": "env-cmd -f .env.staging --no-override npm run build"
      }
    }
    ```