Commit Together by Github VS GitHub Spray

• 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 Creativity
  GitHub Spray allows users to create unique and visually appealing commit histories in the form of complex patterns or graffiti, which can be a fun and creative way to personalize one's GitHub profile.
• Engagement
  It engages users in a playful activity, encouraging them to explore Git and GitHub functionality more deeply while experimenting with their contribution graph.
• Learning Tool
  The tool can be used to teach or learn about how Git records activity, offering insights into how commits work and how they can be manipulated.

Possible disadvantages

• Misleading Contribution Activity
  Creating artificial commit patterns can lead to a misleading representation of user activity, as the commits do not necessarily reflect meaningful or productive work.
• Repository Spamming
  Excessive or frivolous commits can clutter repositories, which can make it difficult for collaborators to navigate the project's history or understand changes.
• Potential for Game-ification
  The focus on visual patterns might encourage game-ification of GitHub contributions, diverting attention from substantive development work and potentially creating unhealthy competition.

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