Commit Together by Github VS LeanKit by Planview

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

• Visual Workflow Management
  LeanKit offers a highly visual interface that allows users to manage their workflows effectively. With customizable Kanban boards, teams can easily see the status of tasks and identify bottlenecks.
• Collaborative Features
  The platform supports real-time collaboration, enabling team members to work together more efficiently. Team members can comment, tag, and update tasks, facilitating better communication.
• Scalability
  LeanKit is designed to scale with teams of varying sizes, making it suitable for both small teams and large enterprises. It supports scaling Agile practices and coordination across multiple teams.
• Integration Capabilities
  LeanKit integrates with a wide range of other tools and platforms, including JIRA, GitHub, and Microsoft Teams, allowing for seamless integration into existing workflows.
• Comprehensive Reporting and Analytics
  The solution provides detailed analytics and reporting features that offer insights into team performance and project progress, helping managers make informed decisions.

Possible disadvantages

• Learning Curve
  New users may encounter a steep learning curve due to the extensive features and customization options available in LeanKit, which might require additional training.
• Complexity for Small Teams
  The extensive feature set might be overwhelming for smaller teams or projects that do not require such robust capabilities, potentially leading to underutilization.
• Cost
  LeanKit can be expensive for smaller teams or startups due to its pricing model, which may not be cost-effective if not all features are utilized.
• Interface Customization Limitations
  Despite having customizable boards, some users find that the customization options for the interface are limited compared to other tools, which might affect usability.
• Performance Issues
  Some users have reported performance issues, especially with larger boards or extensive datasets, which can lead to slower response times within the application.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago

Tracking LeanKit by Planview since Mar 2021.