Content Comparison

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

A: Both instances of Gitlab have now been phased out.

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 enterprise has read access. You can further limit read and write access by changing the individual repo’s settings and/or creating teams and using the teams to grant permissions.

• 'Internal' Visibility Means ReadOnly Access Across the Enterprise

• 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 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.