Risk Classification: Only Low or Moderate Risk data is allowed in Cardinal Cloud GitHub.
There are practical, functional and financial considerations that should be made when storing files, data and code associated with a repository. Exceeding these default limits may result in cost overages, which in turn require an organization to have a linked Cardinal Cloud Azure subscription to accept incurred expenses.
- Repository Size Limit:
- Repositories over 100 GB may experience reduced performance and may be flagged for exceeding the recommended size.
- GitHub Actions minutes and Individual File Size Limit:
- Individual files in a repository should not exceed 100 MB.
- GitHub Actions minutes per month per enterprise is 50,000.
- GitHub Packages storage per organization is 50 GB.
- GitHub Large File Storage (LFS):
- Git Large File Storage (LFS) is used for storing large files up to 1 GB.
- Effective Nov. 15, 2024: A new GitHub billing model has been implemented, increasing the free, included amount of Git LFS resources to 250 GiB of storage and 250 GiB of download bandwidth per month at no cost. For storage beyond the included limits, Git LFS files will incur a cost of $0.07 per GiB per month (USD) and download bandwidth will be charged at $0.0875 per GiB per month (USD).
- GitHub LFS handles large files by replacing them with text pointers inside Git while storing the actual file contents on a remote server.
Storage restrictions for a GitHub repository at Stanford
When using GitHub to store code or other data, do not store any of the following:
- Sensitive Information:
- Passwords or API keys: Avoid storing plain text passwords, API keys, personal identifiable information (PII) like Social Security numbers or addresses, and private cryptographic keys such as SSH keys or SSL certificates in repositories.
- Personal Identifiable Information (PII): Do not include data such as Social Security numbers, addresses, or any other PII.
- Configuration Files with Sensitive Data:
- Database credentials: Configuration files containing database credentials or connection strings should be excluded.
- Cloud service credentials: Do not include credentials for services like AWS, Azure, or Google Cloud.
- Large Files or Binary Data:
- Large files or datasets: Repositories should not store large datasets, videos, or other binary files, as these can bloat the repository. Instead, use Git LFS or other storage solutions for large files.
