Commit Together by Github VS Progress

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

• User Engagement
  Tools like Progress can enhance user engagement by providing visual representations of their achievements, motivating them to continue using the service.
• Goal Tracking
  Progress platforms typically offer a streamlined way to set and track goals, making it easier for users to monitor their progress over time.
• Customization
  Users often have the ability to customize their progress tracking experience to fit their personal needs and preferences.

Possible disadvantages

• Accessibility
  If the platform is down or experiencing technical issues, such as those indicated by a suspended page notification, users may not be able to access their progress data.
• Data Privacy
  Users might be concerned about how their data is stored and used, especially if the platform doesn't have clear privacy policies.
• Learning Curve
  New users may face a learning curve in understanding how to best utilize the platform's features to track their progress efficiently.

• 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 Progress since Mar 2021.