Something Digital VS git-sizer

• Expertise
  Something Digital boasts a team of experienced professionals with vast knowledge in eCommerce solutions, providing clients with high-quality service.
• Client Portfolio
  They have a strong client portfolio with notable companies, showcasing their ability to handle large, complex projects successfully.
• Comprehensive Services
  Offers a wide range of services including eCommerce strategy, user experience design, and managed services, ensuring a holistic approach to client needs.
• Customization
  Provides tailored solutions to meet the unique needs of each client, which can lead to more effective and efficient outcomes.
• Partnerships
  Maintains strategic partnerships with major platforms like Magento and BigCommerce, enhancing their capability to leverage top-tier tools and resources.

Possible disadvantages

• Cost
  Services can be expensive, which may be a barrier for small businesses or startups with limited budgets.
• Complexity
  The comprehensive and tailored approach can sometimes result in more complicated project management and longer timelines.
• Resource Allocation
  Given their large client base, smaller clients might occasionally feel overshadowed or may not receive as much attention as larger accounts.
• Scalability
  While they excel at handling large-scale projects, very small businesses or simple projects might find their services too extensive or unnecessary.
• Geographical Limitation
  Primarily focused on the U.S. market, which might not be ideal for businesses with a significant international focus or presence.

• 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.

Tracking Something Digital since Mar 2021.

• 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