Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

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.

Q: Is it possible to make a repo public?

...

A: You can do either. Github handles SSO slightly differently than other platforms, and you’ll basically need to auth a second time to access any resources that belong to an organization. This means that you can use a pre-existing Github account (and that all of your personal repos will stay as-is) or create a new one if you’d like to keep things absolutely separate. Either way, organization members will not be able to access your personal repos unless they are already set to public visibility or you give them access via another means.

Q: Can I still use an SSH key to access repositories inside of an organization?

A: Yes, although there is a one-time setup step required. Please see: Using an SSH Key to Access Org Resources

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: