Working with Configuration Files

The problem with supporting multiple env files is that it encourages devs to save those in their git repositories, which is a horrible idea from a security standpoint. Since these files often include security credentials for various platforms, they should never be committed into a version control system because they're much easier for people to find and abuse. Instead, they should only be placed on the server they have the credentials for. That way someone would need access to the server's file system to get at your credentials. And if they've gotten that far you've likely got other issues, too.

Pushing .env files to git is considered dangerous, you're right, but pushing one or more of them makes little difference to me. I don't push any of them.