(Official documentation located here, and a getting started manual here)
Git, currently, is one of the largest version control systems in terms of market share, and therefore, there should be no surprise that TD-StorageBay has an entire section dedicated to Git.
Most of this guide will cover functionality that is part of GitLab.
For more help, the help pages and user documentation are available.
This guide only covers the basics that you need to know to get up and running with TD-StorageBay
Once you create a repository, or project, you need a way to access it, unless you plan on doing all your work with the Web IDE.
For this, there are two main methods that are used: HTTPS and SSH.
HTTPS, or secure HTTP, is the main content access method of the internet.
You're even using HTTPS to access this website right now.
Because of its ubiquity, HTTPS access is available nearly everywhere, and is relatively fast.
When accessing a repository over HTTPS, you will be required to give your TDSB username and password when needed (see repository permissions).
One caveat of HTTPS is that if you have set up two-factor authentication, you will not be able to use your password.
With 2FA in place, a Personal Access Token must be configured, and this token will be supplied instead of your password.
PATs used for this purpose must have api access.
The git protocol, provided by the git server daemon, is not provided on TD-StorageBay.
To put simply, this is because, while fast, the protocol is relatively insecure.
The git protocol is now part of HTTPS access, but git:// access is not provided.
This is also the reason why, be default, the Git protocol only provides read access, not write access.
Another reason is that supporting it would require manually locating repositories and manually adding git-daemon-export-ok files into each repository that someone wanted to use the git protocol for.