Quickstart
Get Vale running on your project in about five minutes.
This walks through a first working setup. Each step links to the page that covers it properly, so read on where you want the detail.
1. Install Vale
Use your package manager—brew install vale, choco install vale, or one of the others on the Installation page—then check it worked:
$ vale --version2. Create a .vale.ini
Vale doesn't ship with opinions of its own. It needs a configuration file saying where to keep styles and which to apply, so create one in the root of your project:
StylesPath = styles
MinAlertLevel = suggestion
Packages = Microsoft
[*.md]
BasedOnStyles = Vale, MicrosoftFour things are happening:
StylesPathis the folder Vale will keep downloaded styles in. Add it to your.gitignore.MinAlertLevelis the lowest severity worth reporting.Packagesnames what to download—here, Microsoft's writing style guide.[*.md]applies the styles that follow it to Markdown files.Valeis built in;Microsoftis the package.
See .vale.ini for everything the file accepts.
3. Download the styles
Run this again whenever you change Packages. See Packages for other ways to name one, including a URL or a local path.
4. Lint something
You can pass a directory instead of a file, or a glob:
5. Read the output
Each line is one alert:
The rule name is the useful part: it's <style>.<rule>, and it's how you turn one off. To silence that rule for Markdown, name it in your config:
Severity matters for automation. Only error sets a non-zero exit code, so a CI job fails on errors and passes with warnings and suggestions:
See MinAlertLevel for changing what gets reported, and BasedOnStyles for enabling and disabling rules.
Where to go next
Browse the Package Explorer for styles beyond Microsoft.
Narrow what Vale reads using Scopes.
Put an assistant to work, and hold it to a style, with the Agents guide.
Last updated