Way We Do VS git-sizer

• User-Friendly Interface
  Way We Do offers an intuitive and easy-to-navigate interface, allowing users to quickly create, edit, and manage procedural documents without extensive training.
• Customizable Templates
  The platform provides a variety of customizable templates that can be tailored to fit the specific needs of different business processes and industry standards.
• Real-Time Collaboration
  Users can collaborate in real-time, making it easier for teams to contribute to and update standard operating procedures and workflow documents collectively.
• Version Control
  Offers robust version control features, allowing users to track changes and maintain a history of document revisions, which is crucial for keeping procedures up-to-date.
• Compliance and Audit Support
  Helps ensure compliance with industry standards and regulations by providing audit trails and standardized documentation processes.
• Integration Capabilities
  Integrates with popular business tools and platforms such as Microsoft Office, Google Workspace, and various project management apps, facilitating seamless workflow integration.
• Access Control
  Provides detailed access control settings, allowing administrators to allocate permissions and restrict access based on user roles.

Possible disadvantages

• Cost
  The pricing structure might be prohibitive for smaller businesses or startups with tight budgets, as the cost can add up with additional features and user licenses.
• Learning Curve
  Although the interface is user-friendly, there may still be a learning curve for users who are unfamiliar with process documentation tools or require advanced features.
• Limited Offline Access
  Primarily an online platform, Way We Do requires internet access for most functionalities, which can be a limitation in areas with unreliable connectivity.
• Feature Complexity
  With a wide range of features and settings, some users may find the platform complex to fully utilize without extensive onboarding and continuous use.
• Customer Support
  Some users have reported that customer support response times can be slow, making it challenging to resolve issues promptly.

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

Way We Do - Contract Review Process

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

Tracking Way We Do 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