Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feature request: add `.env` files

See original GitHub issue

This is a feature request to add .env files to identify

Issue Analytics

State:
Created 3 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

1reaction

Cediddicommented, Aug 4, 2022

I guess we can close this issue because 2.5.3 is published to pypi 😃 Thanks Anthony and Thanks Wes.

1reaction

Cediddicommented, Aug 2, 2022

12 factors app is a great methodology, but that doesn’t mean every project which deals with dotenv files has to follow it perfectly. But that doesn’t change the fact that there’s a dotenv file format that’s being widely used, and it should be recognized by this library.

In my case, I’m writing a hook to check SOPS encrypted files, and one of the formats SOPS support is dotenv files (sharing pre-filled .example.env files for development environment setups is something I saw multiple times). Another case might be forbidding dotenv files to be committed via pre-commit hooks. And the last thing that comes to my mind is a linter for dotenv files, (https://github.com/dotenv-linter/dotenv-linter)

So there is indeed a dotenv file format, and there are legitimate use cases for those in the context of pre-commit hooks.

🙏