Jonot VS Commit Together by Github

• Multi-Channel Customer Check-In
  Customers can join a queue using a QR code, web link or self-service kiosk without downloading an app or creating an account.
• Real-Time Queue Management
  Staff can manage queues from any web browser, call the next customer and keep visitors informed through live status pages and lobby displays.
• Hardware-Independent and Resilient Operation
  Jonot works with existing tablets, computers and displays, while local-network ticket calling can help service continue during internet disruptions.
• Multilingual Customer Experience
  Provide check-in and queue information in multiple languages, helping organisations serve diverse customer groups without additional staff effort.
• Custom Branding and Digital Displays
  Customise kiosks, customer status pages and lobby displays with your organisation’s branding, instructions and promotional content.
• Multi-Location and Multi-Queue Management
  Manage multiple service locations and queues from one platform while allowing each location to operate according to its own needs.
• Customer Feedback Collection
  Collect customer feedback after service to measure satisfaction, identify recurring issues and improve the visitor experience.
• Integrations and Webhooks
  Connect Jonot with other business systems and automate workflows using webhook-based integrations.

• 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 Jonot since Jul 2026.

• 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