GitHub Classroom is deprecated as of 28 August 2026 in favor of GitHub's selected partner solutions. The GitHub Classroom website, APIs, and related services have been decommissioned. User accounts, repositories, and organizations created to work with Classroom are unaffected, but some Classroom-only data — classroom and assignment names, tests defined outside of repositories, and LTI-integrated rosters — will be permanently deleted under GitHub's data-retention policies. This completes a transition GitHub announced on 26 May 2026, when new sign-ups ended.

What this means for you

GitHub Classroom was GitHub's free tool for running programming courses on top of GitHub: teachers created assignments backed by template repositories, students accepted them into their own repos, and autograding ran tests against submissions. As of 28 August 2026 that product is gone — GitHub's changelog states the "website, APIs, and related services have now been decommissioned," so the classroom.github.com interface, the assignment/autograding automation, and any integration calling the Classroom API stop working. The good news, stated plainly, is that the GitHub side is untouched: "any GitHub user accounts, repositories, and organizations created to work with Classroom are not affected" — student work already in repos stays where it is. What disappears is the Classroom layer on top: GitHub says some data — "classroom and assignment names, tests defined outside of repositories, and LTI integrated rosters" — will be permanently deleted per its data-retention policies. So if your course roster lived in an LTI integration, or your autograding tests were defined in Classroom rather than committed to the assignment repos, those are the pieces that vanish rather than migrate. This landed on a short timeline for educators: sign-ups already ended on 26 May 2026, and the full decommission followed on 28 August, right as many institutions were setting up for the autumn term.

Where to go

The repositories are safe; the Classroom scaffolding around them is not, so the migration is about capturing anything that lived only inside Classroom before it is deleted. First, export or note your rosters and assignment structure now — LTI-integrated rosters and assignment names are called out as data that will be permanently deleted, so if you need the mapping of students to repositories, record it while you still can. Second, make sure any autograding tests you relied on are committed into the assignment repositories themselves rather than defined in the Classroom UI ("tests defined outside of repositories" are among the data being deleted); tests already in the repos survive because the repos survive. Third, choose a replacement course workflow before the next term: GitHub points educators to its "selected partner solutions" and directs course staff to the GitHub Educator Community Discussion for the recommended options and transition guidance. If you prefer to stay on plain GitHub, GitHub Actions can reproduce autograding (run your test suite on push) and a GitHub organization with per-student repositories can reproduce the assignment-distribution pattern without the Classroom layer.

• GitHub's selected partner solutions for course management — listed in the GitHub Educator Community Discussion linked from the deprecation notice
• Plain GitHub with GitHub Actions for autograding (run your test suite on each push) plus a GitHub organization holding one repository per student, reproducing assignment distribution without Classroom
• A general education/LMS platform (e.g. an institutional LMS, or tools like Gradescope) for rosters and grading, with student code still hosted in GitHub repositories