The GitHub wiki is an anti-pattern

This article argues that GitHub wikis create avoidable operational and governance risks for engineering teams, while a /docs folder keeps documentation versioned with code, reviewable through pull requests, and compatible with existing developer tooling and automation. For CIOs and technology leaders, the strategic implication is that treating documentation as part of the software delivery lifecycle improves quality, auditability, and maintainability, especially as products scale and teams need consistent standards across repos and releases. The recommendation is to centralize docs in the repository and publish them via GitHub Pages or a docs site, using the wiki only as a lightweight pointer to the canonical documentation.