The disappearance of GitHub Classroom
GitHub Classroom will disappear on 28 August 2026. This is not an interpretation or an exercise in reading between the lines: GitHub has announced the shutdown. Nor does it come entirely as a surprise. In the announcement to the education community, the company itself acknowledges that the service had spent eighteen months in maintenance mode: that waiting room where software remains alive, but is no longer something around which one should make too many plans.
In my own classroom practice, I introduce git and GitHub at the start of the academic year through GitHub organisations. I ask students working on the different modules, both at intermediate vocational and higher vocational level, to use the platform, so that they learn the basics of GitHub and its relationship with version control systems — specifically, Git — almost without noticing.
As a teaching tool, this system has flaws. For example, even in private organisations, only members of the organisation — each group, in this case — have access to the organisation’s own repositories, but they all have access to the repositories of the rest of the group. That is a central obstacle if you assess individual work. And that is where GitHub Classroom came in.
Classroom was not a full virtual campus and did not pretend to be one. It turned a GitHub organisation into something like a classroom: it distributed assignments from template repositories, created a private copy for each student or team, and gathered submissions without taking the work out of the platform where much real software is later developed, or indeed any other task related to the specific module, not necessarily software.
GitHub Classroom did few things and some of them with a certain awkwardness, but it solved a recognisable problem. That modesty was probably one of its best qualities.
What is going to happen
Since 26 May 2026, new sign-ups have no longer been accepted. Those of us already using Classroom can continue creating classrooms, assignments and invitations until 28 August. On that day it will no longer be possible to access the service and the website will be withdrawn. The margin, for those of us preparing courses in summer that begin in September, is not exactly generous.
GitHub accounts, organisations and repositories will not disappear. Classroom-specific data will: classroom and assignment names, test histories, information about submissions, rosters integrated through LTI, and some assessment settings.
GitHub sets 4 September as the final deletion date and has published an official export and migration guide. It is accompanied by an export utility that downloads the data to JSON and CSV files using GitHub CLI.
There is another, less visible change: the Codespaces education allocation associated with Classroom, calculated for groups of up to fifty students, is also disappearing. Teachers and verified students will keep their individual benefits, but that classroom-linked pool will no longer exist.
What is lost
The problem is not only that an application is closing. We lose a small layer of teaching infrastructure that handled dull but necessary tasks: creating dozens of repositories, maintaining the relationship between identities and enrolments, distributing exercises, collecting results and making a first approach to Git and GitHub easier. None of this looks especially impressive in a corporate presentation, but you notice it rather quickly when we have to do it by hand again.
GitHub Classroom had limitations and had been showing signs of stagnation for some time. Its interface was not always clear, some operations failed in opaque ways, and managing large courses could require quite a lot of manual work. But it had two important advantages: it was free and it was embedded in GitHub. Students worked in real repositories, with commits, branches, issues, actions and reviews, not in an imitation of those mechanisms inside another campus platform.
We should also look at the calendar. Announcing a closure in May for August leaves little room for those of us preparing courses over the summer that begin in September. Migration is not just a matter of pressing a button. We have to review templates, automated tests, permissions, student documentation and, in some cases, integrations with the institution’s campus platform.
The proposed alternatives
GitHub recommends two associated solutions. The verb matters: it recommends, not replaces.
Codio is a broader platform, with browser-based programming environments, automated assessment and integration with learning management systems. It has a specific procedure for importing classrooms and assignments. It may suit us if we are looking for a complete solution, although it introduces a different provider, a different business model and a different way of working. More features do not necessarily mean it solves the same problem better.
Classroom 50 is closer to the spirit of GitHub Classroom. It is free software, uses repositories and GitHub Actions, and offers both a web interface and a command line. Its first public version appeared on 1 July, so it is a promising alternative, but also a very recent one. It does not seem wise to treat it yet as a perfectly equivalent replacement without first trying it with the materials and the real size of each course. To begin with, it already has a teacher guide and a public support and discussion forum.
There is always a third route: working directly with organisations, template repositories, teams and GitHub Actions (which is probably what I will do). It is a more handcrafted solution and keeps us in touch with the platform, but it gives us back much of the administrative work that Classroom absorbed. It could work well for small groups; it scales worse when each practical exercise generates dozens or hundreds of repositories, which is usually the case.
A transition worth preparing
For those of us who already have active classrooms, the immediate priority is quite concrete: export the information before the closure, check which data lives only in Classroom and keep a clear relationship between students and repositories. After that, we need to test the alternatives with a real assignment, not just compare lists of features.
The disappearance of GitHub Classroom reminds us of something uncomfortable about digital teaching: even a free, useful and well-established tool can disappear when it no longer fits the priorities of whoever maintains it. Free does not mean permanent, and being hosted on GitHub does not mean it is an immovable part of GitHub.
This does not invalidate the work we have done with Classroom, but it does suggest keeping important materials in exportable formats, tests alongside the code, and the design of our courses at a prudent distance from any one interface.
GitHub Classroom solved a small need with a relatively small tool. Its replacement may end up offering more features, but it is not clear that it will offer the same simplicity. And for many classrooms, that was precisely the valuable part.
From a purely personal perspective, in the four years I have been teaching, I have not had major problems with students, and most of them have ended up thanking me for it because they use GitHub extensively at work.
And, in confidence, and since this is a personal blog, I have to say that I started using this tool not because I thought it was a good teaching tool, or a permanent one, but because I came into further education having worked on several European projects that required the use of GitHub and GitLab, so it seemed like a good idea to keep the students occupied with something that would be useful to them and that I already knew how to manage, and which gave me time to prepare the different modules in play. 🤗
References for preparing the transition
- Full shutdown announcement and timeline, including deletion of Classroom-specific data.
- Exporting or migrating GitHub Classroom data, GitHub’s official documentation.
- Classroom Export Utility, the export tool repository.
- Importing GitHub Classroom into Codio, the provider’s procedure.
- Classroom 50 teacher guide, documentation for the free software project recommended by GitHub.