"files.associations":
".env.development.local": "env",
".env*.local": "env"
How this file behaves depends on your stack. Let's look at the heavy hitters.
Imagine a team of five developers. Everyone checks out the same repo. .env.development.local
Because .env.development.local is in .gitignore, Alice and Bob never overwrite each other’s configurations, yet they both inherit the base .env.development settings. "files