Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation provides both Windows and Linux examples for most languages and deployment scenarios, but Windows is often presented first, and Windows-specific tools and terminology (such as PowerShell and Windows runners) are prominent. PowerShell is included as a supported language, with both Windows and Linux templates, but Python is explicitly unsupported on Windows. The documentation references Windows runners and deployment patterns before their Linux equivalents, and some sections (such as workflow template selection and example code) consistently list Windows before Linux. There is limited discussion of Linux-specific considerations or troubleshooting.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Include Linux-specific troubleshooting tips and considerations, especially for deployment methods and authentication.
- Ensure that all language examples provide equal detail for both Windows and Linux, and clarify any platform limitations (e.g., Python not supported on Windows) with rationale.
- Highlight Linux-native tools and patterns (such as bash scripting, Linux file permissions, etc.) where relevant.
- Consider adding a summary table comparing Windows and Linux deployment differences, including supported languages, runners, and limitations.
- Avoid using Windows terminology (such as 'PowerShell') as the default unless the context is truly Windows-specific.
Create Pull Request