From 0b0005b9938eea2804c1cd9b83f9be3329355bc0 Mon Sep 17 00:00:00 2001 From: alex Date: Tue, 15 Jul 2025 13:30:19 -0400 Subject: [PATCH 1/3] add note on dotenv --- docs/tools/dotenv.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/tools/dotenv.md b/docs/tools/dotenv.md index cac2613f..fce90cd5 100644 --- a/docs/tools/dotenv.md +++ b/docs/tools/dotenv.md @@ -18,6 +18,17 @@ Dotenv Linter does not require configuration to run and automatically anlysises ::: +:::info + +CodeRabbit runs Dotenv Linter against the following file patterns: + +- `**/.env` +- `**/.env.*` + +We will not run against files that do not start with `.env` (e.g., `test.env`). + +::: + ## Features Dotenv Linter can detect: From 0c3f52a2e8a1df5acbf27d0c1471f9394b28bbe6 Mon Sep 17 00:00:00 2001 From: alex Date: Tue, 15 Jul 2025 13:31:11 -0400 Subject: [PATCH 2/3] add note on dotenv --- docs/tools/dotenv.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tools/dotenv.md b/docs/tools/dotenv.md index fce90cd5..d39cd047 100644 --- a/docs/tools/dotenv.md +++ b/docs/tools/dotenv.md @@ -25,7 +25,7 @@ CodeRabbit runs Dotenv Linter against the following file patterns: - `**/.env` - `**/.env.*` -We will not run against files that do not start with `.env` (e.g., `test.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. ::: From 42773f3e2e047e19b4baff66b1cd3ebe72419275 Mon Sep 17 00:00:00 2001 From: alex Date: Tue, 15 Jul 2025 13:52:23 -0400 Subject: [PATCH 3/3] fix sidebar --- docs/tools/dotenv.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/tools/dotenv.md b/docs/tools/dotenv.md index d39cd047..a3a2dfd2 100644 --- a/docs/tools/dotenv.md +++ b/docs/tools/dotenv.md @@ -12,21 +12,19 @@ import ProPlanNotice from '@site/src/components/ProPlanNotice.mdx'; [Dotenv Linter](https://github.com/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. -:::note - -Dotenv Linter does not require configuration to run and automatically anlysises `.env` files. If no configuration file is found, it will use default settings. - -::: +## Files -:::info - -CodeRabbit runs Dotenv Linter against the following file patterns: +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. +:::note + +Dotenv Linter does not require configuration to run and automatically anlysises `.env` files. If no configuration file is found, it will use default settings. + ::: ## Features