Recent Posts

Account Archive/Removal for Separated Users

On Tuesday, March 9th, beginning at 11:00 AM, we will be starting the archive and removal process for GitHub accounts for separated users. We anticipate running the removal process on March 15th.

Disabling TLS 1.0 and TLS 1.1

Support for TLS versions 1.0 and 1.1 will be removed for the NC State GitHub service on January 27th at 11:00 AM.

GitHub Upgrade Schedule Change

Historically we have always scheduled upgrades for the NC State GitHub service for Friday afternoons at 5:00 PM. Rather than continuing to rely on the benevolence of GitHub support going above and beyond what we are entitled to, we are modifying our upgrade schedule to avoid outages from upgrades rolling through the weekend. Therefore, we will now be scheduling all GitHub upgrades for Monday at 5:00 PM.

Account Archival and Removal

We will be starting the account archive process at 10:00 AM EST, on Thursday, April 2. There is approximately 15GB of data to process across ~950 accounts. We don't anticipate this process taking longer than the weekend to complete, and hope to have the process finished by the close of business on Friday, if not before. The following Wednesday, April 8, beginning at 10:00 AM EST, we will begin removing the accounts. This process should complete within an hour or so.

Extended Maintenance for Server Migrations

The maintenance is scheduled for March 12th, from 5:00PM to 11:00PM. Contact if you have any questions or concerns.

Delay in Upgrades to 2.20.x

As a part of the 2.20.0 upgrade, there is an optional (for now) migration script that will modify the classification of existing repositories in the instance. At some point in the future, this migration will become mandatory. We'd like to invoke this migration now, but we are unsure what the exact impact to the existing repositories will be. As such, we will be delaying the 2.20.x upgrade until such time as we are able to test the migration script on a development instance of Enterprise Server, and document exactly what the impact will be. Therefore, until we test out the migration script on a 2.20.x instance of Enterprise Server, we will be keeping the deployment on the 2.19.x release branch. This will apply security patches and fix critical bugs, but will not introduce any new features or improvements. We're excited to take advantage of some of the new toys coming in 2.20.x, but we want to make absolutely sure we know what the repository migration impact will be before we roll it out.

User Account Decommissioning – June 14th

In line with our policy for user account decommissioning, on June 14th at 3:00PM we will be starting the decommissioning process for user accounts that...

GitHub TLS Certificate Update

The service uses a TLS certificate to verify its identity to browsers, and ensures that all communication between clients and the server is encrypted...

Creation of

For a while now, we’ve been wanting a place to consolidate documentation for the NCSU GitHub service, but haven’t had a suitable location to put...