SAI360 VS Commit Together by Github

• Comprehensive Risk Management
  SAI360 offers a holistic approach to risk management, integrating various functionalities such as compliance, audit, and incident management into one platform.
• Customizable Modules
  The platform provides customization options to tailor modules and workflows to specific organizational needs, improving efficiency and relevance.
• User-Friendly Interface
  SAI360 features an intuitive, user-friendly interface that makes navigation and task management easier for users, improving user adoption and productivity.
• Cloud-Based Solution
  Being a cloud-based solution, SAI360 offers flexibility and scalability for organizations, along with easy access from anywhere and lower IT infrastructure costs.
• Robust Reporting and Analytics
  The platform provides strong reporting and analytics capabilities, allowing users to generate detailed reports and derive insights for informed decision-making.

Possible disadvantages

• Complex Initial Setup
  The initial setup of SAI360 can be complex and time-consuming, requiring significant effort and potentially external consultation for proper configuration.
• High Cost
  The solution can be costly, particularly for small-to-medium-sized businesses, both in terms of subscription fees and additional customization costs.
• Steep Learning Curve
  Despite its user-friendly interface, the breadth of functionality means that users face a steep learning curve needing extensive training to fully utilize the platform.
• Limited Offline Capabilities
  As a cloud-based solution, SAI360 has limited offline capabilities, which can be a disadvantage for users needing access in environments without reliable internet connectivity.
• Support Challenges
  Some users have reported challenges with customer support, including slow response times and difficulties in resolving complex issues promptly.

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