Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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 and using the groups to grant permissions.

Q: Is it possible to make a repo public?

A: Yes, go to the repo settings. See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility

Q: Can we get our own Github organization for our group/team/department?

A: This is potentially possible, but there are caveats which mean it might not be the best solution in the end. Please see: Notes On Github Organizations

  • No labels