GitHub File Icon VS Commit Together by Github

• Enhanced Visual Differentiation
  GitHub File Icon helps users quickly identify different file types with distinct icons, improving usability and streamlining navigation in repositories.
• Easy Installation
  The extension is easy to install and set up, requiring minimal effort for users to enhance their GitHub browsing experience.
• Customizable
  Users can configure and customize the extension according to their preferences, allowing for personalized use.
• Open Source
  As an open-source project, it allows contributions from the community, fostering collaboration and continuous improvement.

Possible disadvantages

• Browser Dependency
  The extension relies on specific browsers and their extension frameworks, which could limit its availability for users on unsupported platforms.
• Potential Performance Impact
  Adding additional features to GitHub could slightly affect performance, particularly for repositories with a large number of files.
• Maintenance Requirement
  As an open-source project, continuous updates and maintenance are required to ensure compatibility with the latest GitHub changes.
• Limited Audience
  The extension mainly benefits users who frequently browse large repositories, making its value more niche compared to broader GitHub features.

• 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 GitHub File Icon 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