| Table of Contents |
|---|
Q: What is the timeline for sunsetting the on-premise Gitlab instances?
A: No timeline has been identified yet. As things progress, we will be sure to communicate this broadly across multiple channels and with plenty of reminders. We encourage everyone to prefer creating new repositories in Github in order to minimize future migration needsBoth gitlab.tufts.edu and gitlab.it.tufts.edu will be shut off July 1, 2024. If you discover that you need something from these machines after this date, please submit a ticket to escp-ticket@tufts.edu.
Q: Will we have the ability to control who has access to our repositories?
...
A: Yes, although there is a one-time setup step required. Please see: Using an SSH Key to Access Org ResourcesFor additional topics, please see the following page in this wiki: GitHub
Q: Is GitHub Copilot available under our enterprise site license?
A: Yes, a limited number of seats have been licensed for GitHub Copilot for the Tuft Technology Services (TTS) community. See here: GitHub Copilot License Request
For awareness:
Please see TTS Guidelines for Generative AI Tools
Please see GitHub Copilot Product Specific Terms
Note Defense of Third party Claims: Enable the Duplicate Detection Filter in Copilot.