Doc-Warden is an internal project developed by the Azure SDK Team (current version 0.7.3). It is primarily a command-line tool used in CI builds to enforce documentation standards, specifically for READMEs and Changelogs, across Azure SDK repositories. Its release cadence is irregular, driven by the needs and development cycle of the broader Azure SDK Tools project.
pip install doc-wardenVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to use the `ward` command-line tool to perform documentation scans. The tool checks for README and Changelog standards based on a `.docsettings.yml` configuration file. It's designed to be run within a CI/CD pipeline, often targeting the source directory of a repository.
Ensure your environment uses Python 3 (preferably 3.4-3.8, as per historical testing, though newer Python 3 versions generally work).
Thoroughly test your `omitted_paths` configuration. Inspect verbose output (`-v` flag if available, or review logs) to ensure the correct files and directories are being excluded from checks. Refer to the official `azure-sdk-tools` repository for up-to-date `.docsettings.yml` examples.
For .NET projects, define `package_indexing_traversal_stops` in your `.docsettings.yml` to guide Doc-Warden's directory traversal, as .csproj files are often located differently from their documentation. Without this, indexing may not execute correctly.