Roku developer repositories moved from GitHub to GitLab
- ID
- 39212
- Status
- summarized
- Published
- 25 Oct 2026, 12:06 AM
- Fetched
- 25 Oct 2026, 5:42 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://blog.roku.com/developer/gitlab-move
- Source URL
- https://hnrss.org/best
Summary
- Score
- 3.0
- Created
- 25 Oct 2026, 5:42 AM
- Tags
- Audience
- developers
What happened
Roku says it has completed moving all of its developer resources off GitHub and onto GitLab, covering the developer documentation repo, sample apps, and the tooling repositories developers build against, plus open-source software for the RSG 2.0 SDK. Repository names stay the same, and links inside Roku's docs and blog posts have been rewritten to the new GitLab URLs. The only stated action for developers is updating bookmarks or any stored Roku repository URLs that still point at the old host.
Why it matters
If you maintain a Roku channel, this is a small but real chore: any hardcoded github.com/rokudev remotes, submodules, CI checkout steps, or bookmarked sample-app URLs will break or go stale, so grep your build config and swap them for the GitLab equivalents. If you don't ship Roku software, there is nothing to decide here — Roku itself describes the developer impact as minimal, and the post contains no migration deadline, no auth or API changes, and no pricing or licensing change.
Discussion angle
Use the 138-comment thread as a prompt: how many teams actually mirror or self-host their source so a single vendor (GitHub or GitLab) moving or changing terms can't strand their build pipelines — and what would it cost you to add a mirror this quarter?