Version Control provides a history of changes and ability to reference specific versions of source code stored in repositories; used for collaborative software development, testing, and process automation.
Online training, documentation, and other resources are available at no cost: access via the "Explore" link after logging into UT GitHub.
For UT Staff: Don’t Be Afraid to Commit: Intro to Git-GitHub (UT Canvas)
UT FYI Series Git/GitHub Topics
Enterprise Binary Repository (Artifactory)
GitHub is a Git repository hosting service that offers all of the distributed version control and source code management functionality of Git along with a graphical console and tools for bug tracking, task management and collaboration. UT’s GitHub Enterprise instance is hosted on campus and supported by ITS Applications.
New User requesting access? Select Login.
Otherwise, submit a request to:
- Request a new GitHub Organization (UT Faculty and Staff Only)
- Request Assistance/Ask a Question
- Git distributed version control system (DVCS) featuring improved source code management, branching and merging
- User-friendly graphical interface
- GitHub-included toolset for issue tracking, task management, code reviews and collaboration
- Single sign-on (SSO) authentication with granular control of repository access
This service and its offerings are provided as Common Good.
Service availability: 98.37%
Users of the service and identified owners/administrators agree to be aware of and adhere to the university's Acceptable Use Policy. GitHub subscribers agree to:
- Comply with the standards set by the Information Security Office for storing data on GitHub.
- Comply with other university Campus IT Policies, where applicable.
- Be familiar with the university's Minimum Security Standards for Applications Development and Administration when developing applications on GitHub.
- Responsibly use shared resources. ITS reserves the right to disable access without prior notice in the event it is suspected/determined to be having an adverse impact on the service.
- Be responsible for requesting de-provisioning when the developer account is no longer needed.
- Archive or delete repositories that are no longer needed.