Repositories are used to hold files and represent an entity that can have permissions/roles applied to it.  Common reasons for creating a repository would be to hold software project source code, scripts used to setup/configure a service, or documenting some process or procedure.

Repository Types

For Repos that are meant to be available to the GitHub organization, set them as Internal. Internal repos will automatically be visible to all members of our Syracuse University organization.

For Repos that are meant to be available only to yourself or team, set them as "Private".

Create a new GitHub Repository

  • Name for repositories must be unique in the Syracuse University GitHub organization, once a name has been taken you will have to choose another until the repository with the name is deleted - Create Repository
  • Set Team as Admin for the Repository; Remove direct user permission to the newly created repository. - Manage access
  • If the repository is going to be not "Private" then the name should be prefixed with the Team's name that owns the repository. e.g. "ITS-CIS-PowerShell Best Practices" (repository name for an "Internal" repository owned by the ITS-CIS team).
  • It is recommended that the "Description" field be filled in with information describing what the repository contains.
  • All repositories should be set to "Private" initially and can be changed to "Internal" (available to all Syracuse University GitHub users), or "Public" (available to anyone on the internet) if needed.

Other teams can be assigned for other functionality like Maintain, Write or Read.

  • No labels