Repman VS Commit Together by Github

• Private Composer Repository
  Repman provides a private repository for PHP Composer, allowing teams to manage and distribute their PHP packages securely within their organization.
• Improved Dependency Management
  It offers enhanced dependency management tools, which help developers resolve dependencies faster and more efficiently, leading to improved development workflows.
• Access Control
  Repman includes access control features that enable organizations to manage who has access to certain packages, providing better security and collaboration control.
• Caching
  Repman caches packages locally, which can significantly reduce installation times for dependencies, especially in large projects.
• Integration with CI/CD
  The platform integrates well with continuous integration and deployment tools, enhancing automated testing and deployment processes.

Possible disadvantages

• Initial Setup Complexity
  Setting up Repman can be complex, especially for teams without much experience in managing private repositories, requiring some investment in time and understanding.
• Resource Requirement
  Running a private Composer repository can demand additional resources, such as server space and maintenance efforts, which may not be ideal for smaller teams.
• Dependency on External Services
  Like any third-party service, there is a dependency on the provider for uptime and stability, which could impact development if outages occur.
• Cost Implications
  While Repman provides valuable features, organizations need to evaluate the cost against their budgets, especially if free alternatives might suffice for smaller teams.
• Learning Curve
  There can be a learning curve for developers new to using Repman, which might temporarily slow down productivity until they become accustomed to the tool.

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

• Private or self hosted registry options for composer/php dependencies

  Https://repman.io/ its free, used satis before but this is better imo. Source: about 4 years ago

• Packeton - Open source private packagist

  There is this service too, by the way: https://repman.io/. Source: over 5 years ago

• 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