Repositories that are part of UCSB Github may be:
- Public: Accessible to anyone on the internet, without need for a Github account
- Internal: Accessible to all UCSB organization members
- Private: Accessible only to specific individuals or teams
In order to access an "Internal" or "Private" repository, users must:
- Have an active Github account AND
- Be invited to a UCSB Github repository, organization or project
Here's a basic overview of how the process will work for most people at UCSB:
- Sally Student already has a github account that she set up for herself a while ago, but Frank Faculty does not have a Github account at all.
- Frank must follow the Github instructions for how to create a new github account. Once he's done that he can receive an invite.
- Regina, who owns a UCSB Github repository wants to work with Sally and Frank, so Regina invites them via their Github account
- Sally and Frank can now receive an email invitation that includes details and a button to accept the invite
- Sally clicks the button, signs into her github account and then is redirected to sign into her UCSBNetId account through Campus SSO.
- Sally and Frank can now start collaborating with Regina on the code in the organizations or repositories that they were invited to.
Organization, project, and repository owners can collaborate with people outside UCSB, using the "Outside Collaborator" feature of Github. Outside Collaborators will not need to login using an UCSBNetID.
In order to access a UCSB Github repository as an outside collaborator, the outside person must:
- Have an active Github account AND
- Be invited to a UCSB Github repository, organization or project AND
- Be listed by the repository or organization owner as an outside collaborator