PDX Classic VS Commit Together by Github

• Community Engagement
  The Portland Classic is known for its strong ties to the local community, often providing opportunities for local vendors and creating a festival-like atmosphere that engages residents and visitors alike.
• Prestigious Heritage
  As one of the longest-running non-major events on the LPGA Tour, the Portland Classic offers a sense of tradition and prestige that attracts top golfing talents and enthusiastic spectators.
• Charitable Impact
  The tournament is committed to philanthropy, regularly raising substantial funds for local charities, which contributes positively to the community and creates a sense of purpose for both organizers and participants.
• Scenic Location
  Held in Portland, the event benefits from the city’s beautiful natural scenery, making it an attractive travel destination for both players and fans, adding to the overall experience.

Possible disadvantages

• Weather Uncertainty
  Portland can experience unpredictable weather conditions, which could potentially disrupt the event schedule and impact both player performance and audience enjoyment.
• Traffic and Accessibility
  The influx of visitors during the tournament can lead to increased traffic congestion and challenges with transportation and parking, which may be inconvenient for attendees.

• 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 PDX Classic 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