GitHub Classroom has closed: what you still have, and how to run next term
Disclosure: I work on Uppcoder , one of the options listed at the end. The rest is about GitHub Classroom itself and applies whatever you choose. GitHub retired GitHub Classroom on 28 August 2026. If your course ran on it, here is what is still there, what is gone, and what your choices are for the next term. What happened, and when GitHub closed new sign-ups to GitHub Classroom in May and…
On 28 August 2026, GitHub ended its GitHub Classroom service. This service helped educators create student repositories for coding assignments. If you used GitHub Classroom, you can still access what was created, but some data will be permanently deleted. GitHub pointed educators to two partners: Classroom 50, a free, open-source option, and Codio, a commercial platform.
After the retirement of GitHub Classroom, new sign-ups were closed in May and the service was permanently retired at the end of August. Your GitHub accounts, repositories, and organizations created through Classroom are unaffected. Everything that lived in a repository remains where it was, including your classroom organization, student repositories, template repositories, and any tests kept inside repositories.
However, Classroom data is being deleted under GitHub's retention policies. If you haven't already, download your classroom data as JSON and CSV files using the Classroom Export Utility. You can also use the GitHub CLI to list and clone student repositories, and rebuild tests and rosters from your LMS class list or your own records.
For the next term, you have several options. Classroom 50, a free, open-source option from the Fifty Foundation, offers a similar experience to Classroom. Codio, a commercial platform, provides a hosted environment for coding courses with autograding and migration guides. If you choose Uppcoder, a commercial option with a free tier, Uppcoder will move your course assignments for you, and it runs free until 30 June 2027.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
