Roku developer repositories moved from GitHub to GitLab

294 points · 208 comments on HN · read original →

Points and comments are a snapshot, not live.

Roku moved developer repositories from GitHub to GitLab, consolidating docs, samples, and tools.

Roku completed migration of all developer resources from GitHub to GitLab, including documentation, sample apps, and tooling. Repository names remain the same, but URLs changed from github.com/rokudev/<repo> to gitlab.com/rokudev/<repo>. Developers must update bookmarks, Git remotes, submodules, and CI pipelines. Knowledge bases and AI solutions that index repositories need to re-crawl. The "Suggest edits" feature is not supported on GitLab; users can fork and submit merge requests instead.

What commenters are saying

Commenters largely speculated on reasons for the move, citing GitHub outages, Microsoft/OpenAI code scraping, and Roku's internal GitLab use. Some saw it as a positive step against Microsoft dominance, while others noted GitLab has its own outages. A few criticized GitLab's pipeline complexity. One commenter pointed out the readme still referenced GitHub, but a merge request fixed it. Two camps emerged: those supporting the move due to reliability or privacy concerns, and those questioning if GitLab is significantly better.