Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents Windows options before Linux, both in tab order and in explanatory text (e.g., 'Choose either Windows or Linux' with Windows listed first). PowerShell is included as a language with both Windows and Linux tabs, but Python is explicitly unsupported on Windows, indicating a Windows-centric approach. Examples and templates for Windows are consistently presented before Linux equivalents. There is frequent mention of Windows-specific runners (e.g., 'windows-latest') and deployment methods, and Windows deployment details are often given before Linux. The documentation references Windows tools and patterns (such as PowerShell and Windows runners) more prominently than Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples/tabs so that Linux is not always second.
- Provide equal prominence to Linux runners and deployment methods in explanatory text and tables.
- Where possible, use neutral language (e.g., 'Choose your operating system: Linux or Windows') rather than listing Windows first.
- Ensure that all language stacks have Linux examples where supported, and highlight Linux support for languages like Python.
- Add explicit references to Linux tools and shell usage (e.g., Bash) where relevant, not just PowerShell.
- Review all workflow templates and ensure Linux options are equally visible and accessible.
- Clarify any limitations or differences for Linux users early in the documentation, rather than as footnotes.
Create Pull Request