GitHub Classroom is being retired in favor of partner platforms, ending a service that many instructors and administrators used to create assignments, manage rosters, connect learning management systems, and retrieve grades. New sign-ups stopped on May 26, 2026, and GitHub’s published transition timeline placed the Classroom website, APIs, and related services’ decommissioning on August 28, 2026.
The change does not remove GitHub accounts, repositories, or organizations created for Classroom. It does, however, put Classroom-specific management data and integrations at risk of becoming unavailable. Teams responsible for courses should inventory their dependencies, export records they need to retain, and evaluate replacement platforms rather than assuming that repositories alone preserve the complete course history.
What changed in GitHub Classroom
GitHub first stopped accepting new Classroom sign-ups on May 26, 2026. Existing users and classrooms could continue operating during the transition period. GitHub then stated that Classroom would fully transition to partner solutions on August 28, after which users would not be able to sign in to manage classrooms and the Classroom website would be decommissioned. The deprecation announcement states that the Classroom website, APIs, and related services were decommissioned as of that date.
The retirement is separate from the continued availability of ordinary GitHub resources. GitHub accounts, repositories, and organizations associated with Classroom are not affected according to GitHub’s announcements. That distinction matters: a repository may remain accessible even when the Classroom metadata, assignment management, grading records, or roster workflows connected to it are no longer available through Classroom.
The Classroom REST API documentation identifies operations marked for removal on August 28. The documented closing-down operations include listing and retrieving classrooms, listing classroom assignments, retrieving assignments, listing accepted assignments, and retrieving assignment grades. The documentation lists HTTP 410 Gone among the possible response statuses for those operations.
Course workflows affected by the shutdown
Administrators should look beyond repository access when assessing the impact. Classroom supported assignment and grade workflows, as well as classroom and assignment records that were managed through its website and API. Automation that calls the documented Classroom REST operations may therefore stop working even if the underlying repositories continue to exist.
LMS-connected courses also require separate review. GitHub Classroom supported connecting LMS courses through LTI 1.3 and LTI Advantage, importing student identifiers from LMS rosters, and working with roster data from Google Classroom through a separate import process. The documented LMS guidance names Blackboard, Canvas, Moodle, Sakai, and Google Classroom among the tested or verified integrations; Blackboard is described there as community supported.
These integrations should not be treated as automatically preserved by the continued existence of GitHub organizations or repositories. The supplied documentation confirms the functionality that Classroom provided, but does not document a universal post-retirement replacement for each LMS connection, roster import, or synchronization workflow.
Export data before relying on a replacement
GitHub documents a local export path using the GitHub CLI, the GitHub Classroom extension, and the Classroom Export Utility script. The documented output formats are JSON and CSV. Administrators following this path should set up the required CLI and extension, download the utility, follow its README, and verify the resulting files rather than assuming that an export completed successfully or includes every required object.
The available documentation does not establish that JSON or CSV export covers every course object, grade, test, roster, repository, or LTI configuration. It also does not specify a complete retention schedule, backup behavior, recovery process, or post-decommissioning export window. Those limitations make it important to preserve records that have institutional or operational value before permanent deletion occurs, and to confirm any additional requirements with GitHub or the relevant replacement platform.
GitHub specifically states that some Classroom data will be permanently deleted under its data retention policies. The identified categories include classroom and assignment names, tests defined outside repositories, and rosters integrated through LTI. The available information does not support a broader claim that all repositories, grades, tests, or LTI settings will be deleted.
Documented migration destinations
GitHub’s export and migration documentation identifies Codio and Classroom 50 as migration paths. The Codio option points users to Codio’s GitHub Classroom import instructions. The Classroom 50 option points to its Teacher Guide and community discussions.
The supplied Classroom 50 documentation says the platform would become generally available on July 1, 2026, and that it uses GitHub repositories and GitHub Actions for autograding. That information may help teams compare the way existing courses are built, but it does not establish complete feature parity with GitHub Classroom or guarantee that every assignment, grade, test, roster, or configuration can be migrated automatically.
Codio and Classroom 50 should therefore be evaluated against the specific requirements of each course. The available sources do not provide a full partner comparison or confirm that these are the complete set of recommended solutions.
What developers and administrators should do
- Inventory Classroom dependencies. Identify use of the Classroom website, documented REST operations, assignment and grade retrieval, accepted-assignment data, roster synchronization, LTI connections, and any other Classroom-specific workflow.
- Export required records locally. Use the documented GitHub CLI, Classroom extension, and Classroom Export Utility process. Check the resulting JSON or CSV files and determine whether they contain the records needed for teaching, administration, compliance, or historical reference.
- Review repositories separately. GitHub says repositories and organizations are not affected, but that does not mean they contain Classroom metadata, grades, externally defined tests, or LTI configuration. Preserve or reconstruct those records using the documented export process and any additional procedures confirmed by GitHub.
- Evaluate replacement platforms. Follow the Codio import documentation or Classroom 50 Teacher Guide for those specific paths. Test the migration against representative courses instead of assuming that repository and Actions-based workflows provide full Classroom compatibility.
- Revisit LMS and roster operations. Document how each course currently connects through LTI, imports identifiers, or uses Google Classroom roster data. Plan how enrollment and roster handling will work after Classroom retirement.
- Audit automation and failure handling. Locate scripts and services that call Classroom endpoints, especially classroom, assignment, accepted-assignment, and grade operations. Applications should not assume those endpoints remain available; the REST documentation identifies removal and includes HTTP 410 as a possible response.
Availability and remaining uncertainties
The key dates are clear: new sign-ups ended May 26, 2026, existing classrooms were described as usable until August 28, and the website and related Classroom service were scheduled for decommissioning on that date. The primary announcement states that the decommissioning occurred as of August 28. The sources do not establish whether read-only access, support access, recovery, or an additional export period remains afterward.
They also do not provide a complete inventory of removed APIs, webhooks, integrations, or replacement APIs. As a result, teams should avoid treating the documented REST operations as the entire integration surface. The retirement is not described as a vulnerability or security incident, but permanent deletion and incomplete export coverage create operational and record-keeping risks for organizations that need to preserve course history.
