For the last almost 15 years NC State has made use of the GitHub Enterprise Server environment and it has served us well.  Over the years, GitHub has improved their Enterprise offerings in the cloud, but it was still very much a consumer-focused service, until recently.  Our current GitHub licensing for campus includes a Cloud Enterprise tenant and we’re now ready to make the switch.

Why do this?  It removes the delay in feature parity between the hosted and cloud offerings.  It decreases overall server resources in use on premise. In moving the authentication to Entra ID, we get MFA and the ability to handle External Collaborators. And the list goes on.

As there are differences between the environments, and many repos have integrations, actions, webhooks, remotes, and such, it’s not possible for the GitHub service team to do the migration for you. There will be changes that need to be made as part of a migration.  But there are tools available to do alot of the work.

As such, there will need to be alot of coordination and communication, so we will be:

• hosting a Town Hall, primarily targeted at IT staff on February 24th @ 2pm: https://meet.google.com/gsh-afrr-qfj
• doing a “Migrating to GitHub Enterprise Cloud” training course on March 4th @ 3pm.  We will record this session and make it available for on-demand viewing.
• start hosting office hours the week of March 14th. These will run every other week for the rest of the year.
• creating a bunch of Knowledge Base articles about different aspects of the service, the move, differences, and so forth.  Some are already in place.

This is the primary link to save. It includes links to other KB articles and will be updated with training links and other info:
https://ncsu.service-now.com/kb_view.do?sysparm_article=KB0022763

We expect this migration to take the entirety of 2025.  So there’s plenty of time, no need to rush.

From a prioritization standpoint, we’re looking primarily for the first pass of migrations to be IT-related, so that we can fully exercise all of our training and documentation to ensure that they are solid before tackling research and course-based use cases.  So while it’s fine to tell faculty and students that a move is coming, we’d prefer to delay those use case moves till later in the Spring.  This is mostly just to ensure that we have the cycles to answer questions and assist folks.