CNI supports git version control in three sites - github.com, code.jlab.org, and gitlab.jlab.org. Use cases for these three services follow:
code.jlab.org is the User-facing general purpose deployment of the GitLab infrastructure. In addition to the full suite of git-workflow tools, issue tracking, and documentation hosting. It also provides full CI/CD capabilities, model and container repositories. There are no restrictions on public/private repos, off-site and federated access is permitted.
Please review the documentation and FAQs here: https://pages.jlab.org/scicomp/software/code-gitlab-docs/
Github was primarily intended for users and other non-CST division staff who need a place to store and share code. Jefferson Lab uses a cloud implementation. The repositories are under the JeffersonLab organization, and can be centrally managed if needed. There are no current plans for this service to go away, but it should be considered deprecated in favor of code.jlab.org (see below).
NOTE: It is strongly recommended that JLab staff and Users use (and migrate to, when practical) the on-prem code.jlab.org Gitlab service instead of using github.com.
Useful github.com links:
GitLab is a self-hosted solution targeted at CST division staff to manage internal-use-only software repositories. This instance is not accessible from off-site and is not intended for general use. To get started using GitLab with a new account, send a ServiceNow and request to be added to the "JLab gitlab.jlab.org" instance. Unless you are employed by JLab CST, you almost certainly want to use code.jlab.org instead.