Dotenv Linter

CodeRabbit’s guide to Dotenv Linter.

Dotenv Linter is a lightning-fast linter for .env files. It helps ensure your environment files are consistent, typo-free, and follow best practices.

CodeRabbit runs Dotenv Linter v4.0.0.

Files

Dotenv Linter will run on files with the following patterns:

• **/.env
• **/.env.*

We will not run against files that do not start with .env (e.g., test.env). However .env.dev or .env.local is fine.

Configuration

enabled · boolean · default: true

Enable dotenv-linter

.coderabbit.yaml

.coderabbit.yaml

reviews:
  tools:
    dotenvLint:
      enabled: true

Web UI

In your organization or repository settings, go to Reviews → Tools and turn the tool on or off with its toggle.

Dotenv Linter does not require configuration to run and automatically analyzes .env files. If no configuration file is found, it will use default settings.

When we skip dotenv-linter

CodeRabbit will skip running dotenv-linter when:

• No .env files are found in the pull request.
• dotenv-linter is already running in GitHub workflows.

Notes

• All dotenv-linter issues are treated as warnings (dotenv-linter does not distinguish severity levels).

Features

Dotenv Linter can detect:

• Key duplication
• Missing values
• Incorrect formatting
• Invalid characters
• And many more issues

Links

• Dotenv Linter GitHub Repository