Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are always present and often shown immediately after Bash, sometimes with Windows-specific syntax (e.g., backticks for line continuation). There are references to Windows containers and Mono for .NET Framework builds, suggesting Windows-based solutions for certain scenarios. The troubleshooting section explicitly recommends considering Windows containers for .NET Framework workloads, and PowerShell is treated as a first-class scripting environment throughout.
Recommendations
- Explicitly state that Bash examples work on Linux and macOS, and PowerShell is for Windows (or cross-platform PowerShell Core).
- Where Windows-specific tooling or patterns (e.g., Mono, Windows containers) are mentioned, provide equivalent Linux/macOS guidance or alternatives.
- Clarify in troubleshooting that Windows containers are only needed for legacy .NET Framework workloads, and encourage modern .NET usage on Linux.
- Consider showing Bash examples first, as Bash is the default shell on Linux/macOS, and PowerShell is secondary.
- Add a note about PowerShell Core compatibility for non-Windows users.
- Ensure all referenced tools and steps (e.g., Azure CLI, Docker) are available and supported on Linux/macOS, and mention any platform-specific caveats.
Create Pull Request