Roku Completes Migration of Developer Resources from GitHub to GitLab
On 15 October 2026, Roku officially completed the migration of its developer resources from GitHub to GitLab, marking a significant update to its software development infrastructure. This transition includes the company’s software development kit (SDK), developer documentation, sample applications, and tooling repositories, all now consolidated under the new central location at gitlab.com/rokudev.
Developers building channels and applications for Roku’s platform must update their bookmarks, scripts, and development workflows to reflect the new GitLab URLs. While the repository names remain unchanged, meaning a project formerly accessible via a GitHub URL such as github.com/rokudev/ is now hosted at gitlab.com/rokudev/, the change in hosting requires manual updates to any stored URLs. This includes not only bookmarks but also any embedded URLs in scripts, automated processes, continuous integration (CI) pipelines, submodules, and package installations that rely on Git URLs. Failure to update these references could lead to errors or reliance on outdated code, as the original GitHub repositories are no longer actively maintained.
Roku’s official channels, including developer documentation and blog posts, have already been updated to direct users to the new GitLab locations. Developers with local clones of Roku repositories are advised to change their Git remote URLs using commands such as git remote set-url origin https://gitlab.com/rokudev/.git. For projects using Git submodules, the URLs should be updated in the .gitmodules file followed by syncing with git submodule sync. CI pipelines and any systems that fetch release artifacts or install packages directly from Git URLs must also be revised to point to GitLab. Additionally, developers indexing these repositories for knowledge bases or coding assistants need to update source URLs and re-crawl to avoid serving stale content.
This migration aligns with Roku’s recent rollout of the RSG 2.0 SDK, announced in September 2026. The new SDK was planned to be hosted on GitLab from the outset, and consolidating all developer assets on a single platform is intended to streamline management and enhance the developer experience. The move is part of Roku’s broader effort to modernise its developer ecosystem and ensure consistent, up-to-date resources for its community.
Despite the migration’s completion, Roku’s GitHub organisation remains publicly accessible and continues to display numerous repositories. Many of these are marked as archived, indicating they are preserved for reference but no longer receive updates. This archival status suggests a transitional phase rather than a complete removal of the GitHub presence, which means developers should verify the currency of any resources they access there and migrate to GitLab-based repositories as soon as possible.
Developers wishing to contribute to Roku’s documentation can still do so on GitLab by requesting access to the relevant repository, forking it, and submitting merge requests. However, unlike GitHub, GitLab does not support a quick “Suggest edits” feature, so contributions require a more manual process.
Overall, Roku’s migration from GitHub to GitLab represents a significant but necessary technical update. Developers are encouraged to promptly update their links, configurations, and workflows to avoid disruptions and ensure they are working with the most current versions of Roku’s developer tools and resources.