Bias Analysis
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation frequently uses Windows-style paths (e.g., c:\jsontemplates) in command examples and presents Windows path syntax before Linux/macOS equivalents. Some commands (install, upgrade, list-versions) are only available via Azure CLI, which is cross-platform but often associated with Windows. The documentation references Azure PowerShell and Windows-specific path conventions, while Linux/macOS paths are only mentioned in a few sections (e.g., restore cache location). There are no explicit Linux/macOS command examples for file paths in most sections, and Windows paths are shown first or exclusively in many cases.
Recommendations
- For every command example using a Windows path (e.g., c:\jsontemplates), provide an equivalent Linux/macOS example (e.g., /home/user/jsontemplates) side-by-side.
- When describing file paths, mention both Windows and Linux/macOS conventions, or use placeholder syntax (e.g., <output-directory>) and clarify with OS-specific notes.
- Add explicit Linux/macOS installation and usage notes where relevant, especially for commands only available via Azure CLI.
- Avoid referencing Windows tools (like PowerShell) before cross-platform alternatives unless necessary; provide parity in tool recommendations.
- In sections listing cache locations or environment variables, always show all OS variants together.
Create Pull Request