Back to overview
Feature
.gitignore Check
Tells you whether your .env files are really protected from Git.
A .env file is only safe if Git ignores it. Very often that single line is missing – and the file lands in the repo with all its secrets. Env Clinic checks this and hands you the missing lines.
What it does
Env Clinic reads your .gitignore and checks that .env files are reliably excluded, while .env.example can still be committed. If the protection is missing, you get a clear warning.
Why it matters
Once a .env is committed, it stays in the Git history – even if you delete it later. Not making the mistake in the first place is far easier than cleaning it up afterwards.
How to use it
Env Clinic shows you the exact lines to add to your .gitignore.
.env .env.* !.env.example
- Detects missing protection
- Gives you the exact fix lines
- Deliberately allows .env.example