DOC: --no-override flag should be set for env-cmd example#11163
DOC: --no-override flag should be set for env-cmd example#11163rreckonerr wants to merge 1 commit into
--no-override flag should be set for env-cmd example#11163Conversation
|
Hi @rreckonerr! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
By default `env-cmd` WILL override the globally defined env vars, which differs from the default `dotenv` behavior and adds confusion. Refs: react#11162
|
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
Closes #11162
By default
env-cmdWILL override the globally defined env vars, which differs from the defaultdotenvbehavior and adds confusion.Excerpt from dotenv docs
Excerpt from env-cmd docs