Git: Frequently Asked Questions
How do I access GitHub?
- Visit the following link to login: https://github.umn.edu/
- Login using your Internet ID and university password
*note, use your Internet ID only, not your email address.
Who can use github.umn.edu?
Any individual with a University of Minnesota Internet ID; departmental Internet IDs do not work.
How much does it cost?
GitHub Enterprise is being provided by the University of Minnesota as a common-good service to all faculty, staff and students.
What happens to my repositories when I leave the University?
- Students will be removed from the system when they graduate or have failed to register for two consecutive semesters. Before their account and their content is removed, they will be notified via e-mail four weeks in advance and be provided with a chance to move their files to a different service or location.
- Former staff repositories will persist indefinitely, though departments are encouraged to fork employees’ repositories to an active employee before they leave.
What can I not put into my repositories?
- Encryption keys
- Copyrighted material from third parties
- Private or sensitive data
- Large files (MP3s, videos, etc.)
What is the uptime commitment for this service?
- This service is run on servers housed in the University’s data center, and will be affected by any unplanned or planned outages. The University’s uptime commitment for the data center is approximately 99%.
How should I share repositories with my team?
- Use GitHub “organizations” to create teams. See the official GitHub blog post on how to use this. We recommend using a <institution-department-teamname> naming convention. For example, the Academic Support Resources web team is “umn-asr-web”.
How do I grant access to non-University employees?
- An Internet ID with Active Directory access is required for access to github.umn.edu. You may obtain a sponsored account (https://www.umn.edu/dirtools/sponsor) for any non-University employees who need access to GitHub. When requesting an account, make sure that you check the box to request Active Directory access; it is not enabled by default. Unlike sponsored accounts, departmental accounts by policy cannot be granted AD access, so they cannot be used for access to GitHub.
- Alternatively, you could use an external source control solution offered by the vendor or purchased temporarily for the duration of the vendor collaboration/project. If this solution is Git (such as github.com), this would involve the vendor providing repo access to the relevant University employees and then having each of these University developers push their changes to two remotes. I.e. ‘git push vendor_origin master’ and ‘git push origin master’ (at github.umn.edu). Another method would be to have developers push to ‘vendor_origin’ for the duration of the project, and then do a final push/merge to ‘origin’ at the end.
- Basic Git Commands
- Configure Git
- External Git Resources
- Setup a Simple Git Repository
- Setup Git with a Centralized Server
- Share with Others
- Use the University's GitHub Server