Partner XE VS Commit Together by Github

• Integration
  Partner XE offers seamless integration with a variety of third-party applications, which helps streamline workflows and improve productivity by reducing manual data entry.
• Customizability
  The platform provides a high level of customizability, allowing agencies to tailor the system to their specific needs and preferences, enhancing user experience and satisfaction.
• User-Friendly Interface
  Partner XE is known for its intuitive and easy-to-navigate interface, making it accessible for users with varying levels of technical expertise.
• Strong Support and Training
  The platform offers robust customer support and comprehensive training resources, helping users quickly resolve issues and effectively utilize the system.

Possible disadvantages

• Cost
  For small agencies, the cost of implementing and maintaining Partner XE might be relatively high, potentially impacting budgeting and resources.
• Complex Initial Setup
  The initial setup and migration process can be complex and time-consuming, requiring significant effort and expertise to ensure a smooth transition.
• Limited Mobile Functionality
  While the platform provides a mobile version, it may have limitations compared to the desktop version, potentially affecting productivity for mobile users.
• Feature Overload
  The wide array of features and options available might be overwhelming for some users, leading to underutilization of valuable tools and functionalities.

• 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 Partner XE since Jun 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