Skip to content

Getting Started#

Are you new to GitHub.com? Then this is the page for you! If you are coming from github.umn.edu there are some key differences to be aware of.

The two most important things to understand are first that all user accounts on GitHub.com belong to GitHub.com and second, that any Repository marked Public will be public to the entire internet.

User Accounts#

The first time you accept an invite to an Organization in the UMN Enterprise on GitHub.com, if you haven’t already set up your UMN account on GitHub.com (or added that email to an existing GitHub.com account) you will be asked to configure the GitHub.com account for the email that was invited to the org.

In order to keep personal and professional code distinct and ensure the privacy and security of your code, we recommend you create a separate GitHub.com account for your university email.

If you would like to use an existing GitHub.com account, add your UMN email to that account.

When you access resources within the UMN Enterprise on GitHub.com, you will need to verify your UMN InternetID via the Azure SSO. This process will link your University Identity to your public GitHub.com account.

Repository Visibility#

There are 3 levels of visibility/access in GitHub.com.

  • Public: This sets the repository visible to everyone on the Internet and should not contain any University IP. If you have any additional questions, you can reach out to the Owners of your Organization, University Information Security, or DevEx
  • Internal: Internal repositories are visible to all other members of the Enterprise. This is the equivalent to public on github.umn.edu
  • Private: Private repositories are only visible to members of your Organization or those explicitly added as Outside Collaborators

Additional Information#

There is a FAQ page with answers to common questions along with the remainder of this Documentation site. Support information can be found here