Appolo VS Commit Together by Github

• Open Source
  Appolo is an open-source project, which means that anyone can contribute to its development or customize it according to their needs.
• Community Support
  Being hosted on GitHub allows Appolo to benefit from community support, including contributions from developers around the world.
• Documentation
  Appolo comes with detailed documentation that can help users understand its features and how to integrate it into their projects.
• Modular Design
  The project is designed in a modular way, providing flexibility to use only the components that are needed in a particular project.

Possible disadvantages

• Limited Popularity
  Appolo may not be as widely recognized or adopted as some other technology solutions, which could limit the availability of tutorials and third-party resources.
• Potentially Limited Features
  Depending on the specific requirements of a project, Appolo might lack certain features compared to more comprehensive platforms.
• Maintenance and Updates
  The future development and frequent updates of Appolo depend on the community and contributors, which might impact the frequency and speed of issue resolutions.

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

Tracking Appolo since Mar 2021.

• 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