This page discusses the end-of-service for the service May 2022 and alternatives. is no longer in service (June 6, 2022)

The GitHub Enterprise service is retired. While the server is still online, access is restricted (you may see login errors, which are expected) and the server will be taken offline soon.


As announced last summer, now that a campus service for exists, Engineering IT is ending the GitHub service. The server will be taken offline on June 6, 2022. See below for the timeline for that service retirement.

Courses can continue to use through the Spring semester as before, as long as the organization is created before February 4 when creating new organizations will be disabled. Github-dev will not be available for the summer or fall semesters.

Dave Mussulman has been working with CS Instructional Designers and a few courses that use for their course homework submissions to build a very similar model with See the section below for more info.

Our recommendation is that courses that want to explore GitHub features (like Actions) and help pilot the new repo creator tool use that service for Spring 2022. Courses that cannot change for Spring can continue to use the service for this semester only.

If you are using the server for non-course purposes, you should consider (with either a personal account or an institutional organization described below). The service will also sunset into the service, but its timelines and processes have not been decided yet.


  • Friday Jan 7: Login banner on website updated to announce the retirement
  • Friday Feb 4: Users will no longer be able to create new organizations on
  • Monday June 6: will be taken offline (this is a change from the originally posted 6/3 date)

Our communication plan is to send monthly updates to organization owners through May as reminders and prompts to transition tools and documentation.

Piloting the repo-creator service with in SP22

The CS Instructional Designers have been porting the homemade repo-creator web microservice to work with the service. This model functions similarly to how course management has been done, where instructors do a setup at the start of the semester with the repo-creator tool. Students visit that web tool to self-provision their personal repo in a course organization. has some differences from A GitHub username (not necessarily associated with the university) is required to access the service. Illinois sign-on credentials serve as a kind of 2-factor authentication when the student enters the university-service Github organization web site. All Github activity is tracked using the Github username. It is possible to programmatically map GitHub identity to Illinois identity.

The other big difference from to is our recommendation on organizations. Because creating organizations takes additional time and effort, we suggest either using a premade and CS ID supported organization (Illinois-cs-coursework) for your course/semester/student repositories, or creating a single organization for your course through the process at that is to be used across multiple semesters. This is manageable by using better repository naming schemes, and GitHub Teams features as a way to provide access control and grouping for repositories and people.

Documentation for using the new repo-creator tool and the environment is available at  These tools and documentation are under active development: We’re currently looking for more courses to try and these tools in the spring. Many thanks to the CS instructional designers for developing them and supporting this new platform.

If you would like to help explore and develop these options, please let Dave know. The bigger and more diverse our pilot group is, the better our resources will be to help in this transition.

Campus announces a service

The University of Illinois System (AITS) has an agreement for hosting for university projects. This is available to all faculty, staff, and students for a variety of instructional, research, and work projects.

The university license (technically a GitHub Enterprise Cloud) has some advantages over the use of a personal GitHub username and terms.  This type of GitHub configuration ties in university Shibboleth logins into GitHub accounts and gives an institution presence, security, and continuity into GitHub organizations. It also enables the top service tier and quotas from including services like GitHub Actions.

For more information about the campus service, including how to start using it or moving existing organizations under the university license, see

Getting support

For help exploring alternatives to, you can email Dave ( or
We also have regular Zoom meetings with courses teaching with git as a part of a pilot group/community of practice. If you're interested in joining those meetings, please let Dave know.