Cloudback.it VS git-sizer

• Automated backups
  Scheduled GitHub repository backups
• Configurable schedule
  Various backup schedules supported
• Cloud storage providers
  Azure, AWS S3, AWS Glacier, Google Cloud, Alibaba Cloud, built-in Cloudback storage
• Easy to use
  On click setup
• Microsoft Azure Blob Container support
  Use your own Microsoft Azure Blob Container to save backups
• Amazon S3 Bucket support
  Use your own Amazon S3 Bucket to save backups
• Amazon S3 Glacier support
  Use your own Amazon S3 Glacier to save backups
• Google Cloud Storage Bucket support
  Use your own Google Cloud Storage Bucket to save backups
• Alibaba Cloud Object Storage Service support
  Use your own Alibaba Cloud Object Storage Service to save backups
• Metadata backups
  The backups include the repository metadata such as issues, labels, milestones, and comments
• Download backup
  Download entire backup: repository and metadata
• Restore backups
  Easy to restore the backup as a new GitHub repository

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Cloudback.it yet.

• I have fucked up please please helpp

  If you were using GitHub Desktop, then the file should be in the recycle bin. See this SO answer for more details. You can also try using git restore command. Finally, you can use backup tools like Cloudback to protect your... Source: over 3 years ago

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago