{"repo":"wemake-services/dotenv-linter","free":true,"listed":false,"github":"https://github.com/wemake-services/dotenv-linter","clone":"git clone https://github.com/wemake-services/dotenv-linter.git","description":":relaxed: Linting dotenv files like a charm!","language":"Python","stars":305,"topics":["dotenv","dotenv-parser","linter","code-quality","linting"],"license":"MIT","category":"dev-tools","readme_excerpt":"dotenv-linter --- Simple linter for .env files. While .env files are very simple it is required to keep them consistent. This tool offers a wide range of consistency rules and best practices. And it integrates perfectly to any existing workflow. Read the announcing post. Installation and usage And then run it: See Usage section for more information. Examples There are many things that can go wrong in your .env files: And much more! You can find the full list of violations in our docs. Pre-commit hooks dotenv-linter can also be used as a pre-commit hook. To do so, add the following to the .pre-commit-config.yaml file at the root of your project: For the more detailed instructions on the pre-commit tool itself, please refer to its website. Gratis Special thanks goes to Ignacio Toledo for creating an awesome logo for the project.","default_branch":null,"files":null,"tree":[],"storefront":"/r/wemake-services","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/wemake-services/dotenv-linter/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}