Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash throughout, and is explicitly listed as a prerequisite alongside Bash. There is a slight Windows bias in the repeated mention of PowerShell, the use of PowerShell variable syntax, and the assumption that users may be using PowerShell locally. The prerequisites mention 'a Bash and PowerShell command shell' but do not mention Linux shells or environments specifically. There are no explicit Linux-only examples, and Windows tools (PowerShell) are always presented as an equal option, sometimes before Bash. There is also an assumption that VS Code is the editor, which is cross-platform but often associated with Windows.
Recommendations
- Clarify that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash), and that PowerShell is primarily for Windows users.
- Add explicit references to Linux/macOS environments in the prerequisites, e.g., 'Linux/macOS terminal' or 'Bash shell on Linux/macOS'.
- Consider listing Bash examples before PowerShell, or noting that Bash is the default on Linux/macOS.
- Where PowerShell is mentioned, add a note that it is most relevant for Windows users.
- Provide guidance for Linux users on installing prerequisites (e.g., Python, Node.js, Java) using native package managers.
- Ensure that all steps and code samples are tested and confirmed to work on Linux/macOS as well as Windows.
Create Pull Request