Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is given equal prominence to Bash, which may indicate a Windows bias. There are several references to Windows-specific concerns (e.g., Mono/.NET Framework, suggesting Windows containers for certain workloads). Troubleshooting and agent setup sections mention Windows containers as alternatives, and PowerShell is always presented as a first-class option, sometimes with more detailed syntax. There are no Linux-only examples, and Windows-specific build concerns (Mono, .NET Framework) are discussed before Linux alternatives. The documentation does not mention Linux-specific tools or patterns, nor does it provide guidance for Linux desktop users (e.g., using native Linux package managers, shell environments, or alternatives to PowerShell).
Recommendations
- Present Bash examples before PowerShell to reflect the default shell on most CI/CD runners and Linux environments.
- Add explicit notes or sections for Linux users, such as using native Linux package managers (apt, yum) for prerequisites.
- When discussing .NET Framework and Mono, clarify that these are Windows-specific concerns and provide Linux-first alternatives (e.g., .NET Core/5+).
- Include troubleshooting steps for common Linux issues (e.g., permissions, SELinux/AppArmor, systemd integration) alongside Windows-specific troubleshooting.
- Reference Linux desktop environments and workflows where relevant, such as using GNOME/KDE tools or Linux-native authentication methods.
- If PowerShell is mentioned, clarify its cross-platform nature and provide guidance for users who prefer Bash or other shells.
- Avoid suggesting Windows containers as the primary solution for .NET Framework workloads; instead, recommend modern .NET versions that run natively on Linux containers.
Create Pull Request