Commit Together by Github VS For a Fact

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

• Clarity
  Using 'for a fact' provides clear and direct affirmation, leaving no ambiguity about the certainty of the statement.
• Emphasis
  The phrase adds emphasis to a statement, reinforcing the speaker's confidence in the truth of the information.
• Simplicity
  It is a straightforward and commonly understood expression that easily conveys certainty.

Possible disadvantages

• Overuse
  Frequent use of 'for a fact' can diminish its impact and make the speaker appear overly assertive or dogmatic.
• Informality
  The phrase may be too informal for certain professional or academic contexts where more precise language is preferred.
• Limited Use
  It is not versatile and is mainly used only to express certainty, lacking flexibility for other contexts.

• 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 For a Fact since Mar 2021.