SaaS 1000 VS Commit Together by Github

• Industry Recognition
  Being listed in the SaaS 1000 provides companies with recognition as a leading player in the SaaS industry, enhancing their credibility and prestige among peers and potential customers.
• Visibility and Exposure
  Inclusion in the list increases a company's visibility and exposure, potentially attracting new customers, investors, and partners who follow industry trends and seek reputable SaaS providers.
• Networking Opportunities
  Listing can facilitate networking opportunities with other listed companies, fostering potential collaborations and partnerships within the SaaS industry.

Possible disadvantages

• Competitive Pressure
  Being ranked might encourage competitors to strive for improvement and intensify the competitive landscape, potentially challenging newly listed or lower-ranked companies.
• Focus on Growth Over Sustainability
  The ranking system may prioritize rapid growth over sustainable long-term practices, which could pressure some companies to prioritize short-term metrics over long-term stability.
• Exclusion Risk
  Companies that fail to make the list might suffer from a perceived lack of legitimacy or attractiveness in the market, despite potentially having solid business operations.

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

No analysis of Commit Together by Github yet.

Tracking SaaS 1000 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