Phabricator VS git-sizer

• Comprehensive Toolset
  Phabricator offers a wide range of tools including code review, repository hosting, bug tracking, project management, and more, all integrated into one platform.
• Customizability
  Users can customize workflows, forms, and other aspects to fit the specific needs of their projects.
• Powerful Code Review
  Phabricator provides advanced code review features like inline comments, custom fields, and audit trails, making it a robust tool for maintaining code quality.
• Open Source
  Being open-source, Phabricator allows organizations to host their instance, providing control over data and customizations without licensing fees.
• Multi-repository Support
  It supports multiple version control systems (Git, Mercurial, and Subversion) and allows managing multiple repositories within the same project.

Possible disadvantages

• Complex Setup
  Phabricator can be challenging to install and configure, requiring a good level of technical knowledge and infrastructure.
• Steep Learning Curve
  New users might find it difficult to navigate and use all the features due to its extensive functionalities and less intuitive user interface.
• Limited Third-Party Integrations
  Compared to other platforms, Phabricator has fewer integrations with third-party tools, which might be a limitation for some teams.
• Dependency on Phacility's Future
  Phacility announced that they will cease operations, which means the future maintenance and updates of Phabricator could be uncertain.
• Performance Issues
  For large-scale projects with many users and repositories, Phabricator may experience performance issues and could require significant resources to run smoothly.

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

Phabricator code review session at Wikimedia Hackathon Zurich

More videos

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

• Migrating from Phabricator to Azure Devops. Have some questions.

  My company has used Phabricator, which is an alternative to Azure Devops, for about 5 years. A few days ago they announced that the project won't be maintained anymore, so we are looking into alternatives. We have around 50 devs+product... Source: over 5 years ago

• Is there any "Unified HUB SOlution" in this Microservices era?

  You also mention Gitlab is close to what you would like - maybe Phabricator is even closer: https://phacility.com/phabricator/. Source: over 5 years ago

• Is there an alternative to open project with the next characteristics ?

  Https://phacility.com/phabricator/ I think checks most of those boxes, maybe all. Source: over 5 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