Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell examples are always shown alongside Bash, sometimes with Windows-specific syntax and tools (e.g., New-AzResourceGroup, New-AzContainerAppManagedEnvironment). There are several notes and troubleshooting steps that recommend or mention Windows containers and Mono for .NET Framework builds, suggesting Windows as a solution for certain scenarios. However, Linux parity is generally maintained, and Bash examples are present throughout. The order of presentation sometimes puts Bash first, but Windows/PowerShell is always present and sometimes referenced in troubleshooting and recommendations.
Recommendations
- Clarify that Bash commands work on Linux and macOS, and PowerShell is for Windows users.
- Explicitly state platform compatibility for each command example.
- When mentioning Windows containers as a solution (e.g., for .NET Framework), provide equivalent Linux guidance or alternatives.
- Add troubleshooting steps for common Linux/macOS issues, not just Windows-specific ones.
- Consider grouping platform-specific instructions in separate sections or tabs for clarity.
- Ensure that Linux and macOS users are not required to use Windows-only tools or patterns.
Create Pull Request