Drunkdeck VS Commit Together by Github

• Entertaining
  Drunkdeck offers a fun and entertaining way to enjoy a social gathering or party, providing unique and engaging drinking games.
• Variety
  The platform includes a variety of game modes and challenges that cater to different preferences and group dynamics, ensuring a fresh experience each time.
• Accessibility
  Being an online platform, Drunkdeck is easily accessible from different devices, allowing players to enjoy games from anywhere.
• Social Interaction
  Encourages social interaction and bonding, making it a great tool for icebreaking or enhancing a party atmosphere.

Possible disadvantages

• Encourages Excessive Drinking
  The nature of the platform promotes alcohol consumption, which may lead to excessive drinking and associated risks.
• Limited Appeal
  The platform is primarily focused on drinking games, which may not appeal to individuals who do not consume alcohol or prefer other types of games.
• Potential For Misuse
  Users might misuse the platform in scenarios where drinking is inappropriate or illegal, such as with underage participants.
• Lack of Regulation
  There may be a lack of regulation over the content and scenarios on the platform, potentially leading to inappropriate or unsafe challenges.

• 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 Drunkdeck since Jan 2023.

• 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