As a service provided by the university, all official university policies and regulations apply to the NC State GitHub service. In particular please note the following:
– https://policies.ncsu.edu/policy/pol-10-00-01/
– https://policies.ncsu.edu/regulation/reg-08-00-02/
– https://policies.ncsu.edu/regulation/reg-08-00-03/
Please consider the type of data that you are placing into this system. Remember, every time you store or share sensitive data, it’s your responsibility to fully comply with the NC State Data Management Framework (DMF).
The NC State GitHub Enterprise Cloud service is approved for Red data and below.
Thank you in advance for your help in safeguarding university data.
For assistance related to the NC State GitHub Enterprise Cloud service, please contact the NC State Help Desk via the NC State IT Service Portal or call 919.515.4357 (HELP).
Please do not contact GitHub support regarding your NC State account or repositories.
Use of the NC State GitHub service is free to use for all currently enrolled students, student facing faculty, and non-faculty staff employees of NC State University for the duration of their time at the university. Accounts are automatically provisioned and suspended based on HR and Student Information System (SIS) data.
No-Pay and Workshop accounts are permitted access to GitHub for anyone performing academic, not-for-profit research on behalf of or in collaboration with the university for as long as their account remains active.
Service accounts are available to faculty and staff for purposes of facilitating automation. Service accounts must be approved by the NC State GitHub Service Team before they are available for use in GitHub.
Service accounts are audited once a year by the NC State GitHub Service Team to ensure inactive accounts are disabled and removed.
External guest accounts can be provisioned upon request. Please contact the GitHub Service Team for more information.
Access to the NC State GitHub instance outside the aforementioned usage is not permitted.
Any intentionally malicious usage will result in a ban from the service.
Prior to leaving the University, employees and graduate students should consult the Department Offboarding Guide.
Once a user has become separated from the university, their GitHub account will be automatically suspended and scheduled for removal. A user is classified as “separated” if and only if they do not have an active employee record, are not currently registered for classes, and do not have an active academic plan for the current semester.
All repositories directly owned by the user account will be archived and sent to the user via Google Drive. After the data has been archived, the account will be deleted.
Repositories owned by other users, or which are held under an Organization, will not be included in the repository archive.
Users who wish to include repositories from organizations or other users in their archive should make a copy of the repository in their user account prior to separation.
Any forks of private repositories will be deleted when the original owner's account is deleted.
Users may request a hold be placed onto their account to prevent it from being deleted by contacting the GitHub Service Team; however, the account will remain suspended and inaccessible until such time as the user is no longer classified as separated, at which point the account will automatically be reactivated. In order to comply with our GitHub license agreement, user accounts cannot be reactivated through any other means.
Workshop accounts are recycled regularly after they have been checked in. All repositories and permissions are removed from the account, and no data archive is created for the account.
We highly recommend Workshop account users backup and remove their data from GitHub before they lose access to the account.
Organizations are created upon request by the GitHub Service Team. Separate organizations are approved for any Division/College (two digit OUC), or Unit/Department (four digit OUC), and for any cross-organizational research or IT collaboration. To better comply with security best practices, units are encouraged to make use of organizational structures provided by GitHub to consolidate their repositories into a single organization, where possible.
All organizations within the GitHub Enterprise Cloud environment share a namespace with the public github.com organizations. Therefore, all organizations are prefixed with "ncstate" to avoid naming collisions. In the event a desired name is unavailable, the GitHub Service Team is not able to force renames for external organizations.
Organization owners should not rename their organization. Please contact the GitHub Service Team if you'd like to rename your organization.
The base membership permissions for all organizations is set to "No Permissions" by the Enterprise policy, and cannot be overridden.
It is highly recommended to create and utilize Teams within your organization to assign permissions to repositories.
User repositories are owned by their creator, and the owner has sole discretion for assigning other users permissions to access the repository.
Users are only able to create private repositories under their own account, and must grant explicit access to share the repository with other users.
Organization repositories are owned by the organization, and permissions are assigned as configured by the organization settings.
Any additional access requests should go though the repository owner, or a user with delegated permissions.
The contents of a repository are pursuant to University Policy 10.00.01 and generally content in repositories owned by a student is property of the student, while content in repositories owned by an employee is property of the university. The GitHub Service Team will not provide access to repositories or export data, except through the account archive process during separation.
In cases where the owner is unable or unwilling to grant access, and the contents of the repository are university property, a department head may reach out to the NC State GitHub Service Team to request access, and ownership of the repository will be transferred to an appropriate party.
Any user may create a new repository at any time. A user may create any number of repositories.
Repositories may be named anything. Repositories are always scoped to a user account or organization, so there is no risk of naming conflicts with other users.
Repositories with names that are deemed offensive will be renamed and the owner will be notified of the change.
Repositories are subject to certain limits regarding file size and overall repository size. These limits are imposed by GitHub and cannot be changed.
The Large-File-Storage (LFS) feature is disabled in the NC State GitHub Enterprise Cloud service until a change-back model can be implemented to pay for its usage.
Central management of GitHub Copilot licenses is currently disabled in the NC State GitHub Enterprise Cloud service until a change-back model can be implemented to pay for their usage.
Units may separately purchase individual licenses directly from GitHub until central management is available.
GitHub Actions are automation workflows which can be added to a repository to facilitate tasks such as automated testing and deployment. This feature is available to all users and organizations in the NC State GitHub Enterprise Cloud service. The NC State GitHub Service Team does not provide general support for implementing Actions, but can assist with configuring Action Runners and can provide general advice.
GitHub hosted Action Runners are disabled in the NC State GitHub Enterprise Cloud service until a change-back model can be implemented to pay for their usage.
The NC State GitHub Service Team maintains a pool of Actions Runners which are available for use by any organization in the service. These Action Runners are built from the same initial configuration as the Action Runners hosted by GitHub, and provide a suite of useful software. The Enterprise Actions Runners are a shared service, and workflows are processed in the order in which they arrive. There may be a queue for workflows to be processed. If a workflow is found to be negatively impacting the health of the Enterprise Actions Runners, the workflow may be disabled by the service team and the owner will be notified.
Enterprise Action Runners are only available for repositories within organizations. User owned repositories must use a self-hosted Action Runner.
Any user or organization is free to set up and configure their own Actions Runners for their own use. The NC State GitHub Service Team is not responsible in any way for the maintenance, security, or support of self-hosted Actions Runners, and users who opt to set up and use a self-hosted Actions Runner do so at their own risk.
Regardless of the type of Action Runner, repositories may utilize Actions from Verified Creators in the GitHub Marketplace in their workflows. Additional Actions may be requested for approval by the GitHub Service Team.
Artifacts and Logs from workflow execution are kept for a period of 30 days by default, after which they are deleted and are inaccessible. This limit may be lowered by organizational configuration, but may not be increased.