Virtual Fidget Spinner VS Commit Together by Github

• Accessibility
  Virtual fidget spinners can be accessed from any device with an internet connection, making them available to a wider audience regardless of physical location.
• Cost-effective
  Unlike physical fidget spinners, virtual versions often come at no cost, allowing users to enjoy the experience without financial investment.
• No Physical Clutter
  Using a virtual fidget spinner eliminates the need to store or carry around a physical object, reducing physical clutter.

Possible disadvantages

• Lack of Tactile Feedback
  Virtual fidget spinners do not provide the tactile sensation that physical spinners offer, which can be less satisfying for those seeking a hands-on experience.
• Screen Dependency
  Using a virtual fidget spinner requires a screen, which can contribute to increased screen time and potential digital fatigue.
• Limited Sensory Engagement
  Unlike physical spinners, virtual ones often engage fewer senses, potentially making them less effective for stress relief or sensory stimulation.

• 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 Virtual Fidget Spinner 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