Code Review by Codementor VS git-sizer

• Expert Feedback
  Codementor provides access to experienced developers who can offer high-quality code reviews, ensuring that your code adheres to best practices and industry standards.
• Quick Turnaround
  Codementor aims to deliver code reviews in a timely manner, which can help speed up the development process without significant delays.
• Improved Code Quality
  Professional code reviews can lead to improved code quality and fewer bugs, as potential issues are identified and rectified early in the development cycle.
• Learning Opportunity
  Developers can learn from the feedback given by mentors, discovering new techniques, languages, or best practices they can apply in future projects.
• Flexible Engagements
  Codementor offers flexible engagement options, from one-time reviews to ongoing mentorship, allowing developers to choose the level of support they need.

Possible disadvantages

• Cost
  Engaging with professional mentors can be expensive, especially for individual developers or small startups with limited budgets.
• Varying Quality
  The quality of code reviews might vary depending on the mentor's expertise and experience, potentially leading to inconsistencies in feedback.
• Dependency on External Reviews
  Relying heavily on external code reviews might slow down the internal review and development processes if waiting for external feedback becomes a bottleneck.
• Limited Context
  External reviewers might lack context about the specific needs and goals of a project, which could lead to suggestions that may not be fully aligned with project objectives.
• Communication Challenges
  Coordinating with external mentors could introduce communication challenges, particularly around clarifying feedback and understanding specific recommendations.

• 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 Code Review by Codementor yet.

Tracking Code Review by Codementor 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