Page Comparison

Q: What is the timeline for sunsetting the on-premise Gitlab instances?

A: Both 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. By default, a repo created in one of the organizations under the Tufts enterprise will be “internal,” which means that anyone in the org has read access. You can further limit read and write access by changing the individual repo’s settings and/or creating groups teams and using the groups teams to grant permissions.

• See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility

• and: https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams

...

A: Yes, although there is a one-time setup step required. Please see: Using an SSH Key to Access Org Resources For 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.