From 14a296138bc051129b0b2fcf6e21de3af6a3fc27 Mon Sep 17 00:00:00 2001 From: jdkato Date: Mon, 28 Aug 2023 10:52:12 -0700 Subject: [PATCH] Add `VALE_CONFIG_PATH` to search process docs --- content/en/docs/topics/config/index.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/en/docs/topics/config/index.md b/content/en/docs/topics/config/index.md index fa637102..f2c00aa7 100644 --- a/content/en/docs/topics/config/index.md +++ b/content/en/docs/topics/config/index.md @@ -278,14 +278,15 @@ This is a steward that raises an alert. {{< alert icon="👉" >}} You can override the default search process by manually specifying a path using -the [--config](/manual/config/) option. +the [--config](/manual/config/) option or by defining a `VALE_CONFIG_PATH` environment variable. {{< /alert >}} Vale expects its configuration to be in a file named `.vale.ini` or `_vale.ini`. It'll start looking for this file in the same folder as the file -that's being linted. If it can't find one, it'll search up to 6 levels up the -file tree. After 6 levels, it'll look for a global configuration file in the OS -equivalent of `$HOME` \(see below\). +that's being linted. If it can't find one, it'll search up up the file tree. + +If no ancestor of the current directory has a configuration file, it checks for +a global configuration file in the OS equivalent of `$HOME` \(see below\). | OS | Search Locations | | :------ | :--------------------------------------------------- |