/
Misc Github FAQs

Misc Github FAQs

Here are some GitHub related FAQ for the College of Engineering. Many of these were previously their own separate mini articles

http://github.ucsb.edu run by the College of Engineering for Engineering Students was replaced in 2020 with a different version of Github run by Information Technology Services (ITS) and open to all UCSB students.  Please see https://github.com/ucsb/github-guide for support. Please contact ITS directly at https://www.it.ucsb.edu/help-support/it-services-catalog or for support https://www.it.ucsb.edu/help-support/it-services-catalog

As a disclaimer, we are maintaining pages about GitHub in our Knowledge Base solely so members of the College of Engineering can easily find information. We do not run the service anymore and if there is any disagreement between what is posted here and what is posted on github.ucsb.edu please take what is posted by ITS as the current correct answer, especially if it is something that can change based on policy decisions from ITS like max repo size, acceptable names for sub organizations, etc.. 

The SSH fingerprint for github.ucsb.edu at the time of the migration was:

    53:6d:7e:38:a2:5d:84:ee:64:23:4c:f0:a9:6b:da:c9 (RSA)

This key has been changed due to system software updates post migration.

As this service is no longer run by ECI, we will no longer be publishing the new fingerprint here.

Organizations are a way to simplify management of group-owned repositories and fine tune permissions.

For more info please see the following: https://github.com/blog/674-introducing-organizations

When creating an organization we ask that you append

Prefix: All organizations should begin with "ucsb-".

Identifier: The identifier should be a recognizable name that relates the repo to a department in the format "id-". For student organizations not related to a department stu- should be used.

Postfix: The postfix should be descriptive of the organization, such as the purpose or name of the team/lab.

and finally “-Org” to the end of the name.

example: ucsb-coe-example-org

This is so that organization names don’t conflict with anything else in our name space (like accounts).

Organization names will be checked and may be renamed if they don’t conform to this convention.

As github.ucsb.edu is now run by ITS/ETS they now have final say on what is considered an acceptable name. https://github.com/ucsb/github-guide/blob/main/Organization_Naming_Standard.md

For push, clone, or any other operation involving the github.ucsb.edu server you should be using either https or ssh as the protocol.

This will encrypt your credentials on the network and is generally safer.

You should not store any private or sensitive data, such as passwords or private keys, in any of your repos.

Additionally, media and binary files are not well suited to be used in GitHub.

GitHub is intended as a source code repository.

Please see http://copyright.universityofcalifornia.edu/ownership/index.html for the latest policies.

Yes this is certainly possible, as laid out in this article:

https://enterprise.github.com/help/articles/moving-a-repository-from-github-com-to-github-enterprise

There are number of clients available to perform GitHub operations.

These range from command line interfaces (CLI) to fully fledged GUI programs such as those listed below, for Windows and Mac respectively:

https://windows.github.com

https://mac.github.com

There are many others and github.ucsb.edu has a few more recommendations posted

 Related articles