Reviewable VS git-sizer

• Detailed Review Process
  Reviewable offers a highly customizable review process that allows teams to define their own criteria for code reviews. This flexibility can enhance the quality of code by ensuring thorough checks and balances.
• Integration with GitHub
  The platform integrates seamlessly with GitHub, which is beneficial for developers already using GitHub as their primary code repository. This integration enables streamlined workflows without the need to switch between multiple tools.
• Real-time Collaboration
  Reviewable supports real-time collaboration, allowing team members to see changes and comments as they happen. This feature can enhance communication and the speed of the review process.
• Advanced Commenting Features
  The tool offers advanced commenting features, such as single-threaded discussions and the ability to mark issues as resolved, which can help keep feedback organized and clear.
• High Customizability
  Users can tailor the review process with various configurations, such as review state tracking and custom checklists. This customizability allows teams to adapt the tool to their workflow needs.

Possible disadvantages

• Complex Setup
  The initial setup of Reviewable can be complex and time-consuming, especially for teams not familiar with configuring such tools. This can create a steep learning curve for new users.
• Cost
  Reviewable is a paid service, and the cost can be a concern for small teams or individual developers, especially when considering other free or cheaper code review options.
• Limited to GitHub
  As Reviewable is designed specifically for use with GitHub, teams using other version control systems like GitLab or Bitbucket won't be able to integrate the tool into their workflows.
• Overwhelming Feature Set
  While Reviewable offers numerous features, this extensive set can be overwhelming for new users who may not need all of the functionalities, leading to potential underutilization.
• User Interface Complexity
  Some users may find the user interface complex, with a high amount of information displayed at once. This can make it difficult to navigate for those who prefer simpler, more straightforward interfaces.

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

Reviewable -- what is the fastest way to check out your review code?

No git-sizer videos yet. You could help us improve this page by suggesting one.

• A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev

  Reviewable.io — Code review for GitHub repositories, free for public or personal repos. - Source: dev.to / over 2 years ago

• The GitHub for Code Review UI Needs Serious Innovation

  Yep, I agree! I work at, and use, Reviewable (https://reviewable.io) and we're the best way to review code on GitHub because we've focused on making the whole process better at every step. We've improved diffing, not only for large files... - Source: Hacker News / about 3 years ago

• Software Engineering at Google

  Https://reviewable.io is the earliest full-powered Critique alternative for GitHub. It supports some cool things Critique doesn't/didn't, such as reviewing multi-commit branches (also across history-rewriting force-push cleanups), and... - Source: Hacker News / about 3 years ago

View more

• 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