Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
When I created this fork, that repo wasn't officially supported and the way it did branches and tags was incompatible with how packagist expects those to be set up. I haven't really had time to see if the latter reason has changed since they made it the official mirror of the main dev repo, but it's certainly something to look into. It would be much easier to maintain this repo as a fork from the main repo.
The branches are still in a format that is mostly unusable by packagist as-is, which means every single branch would have to have the version defined in the composer.json in its branch. They do this to get around collisions between branches and the first stable release of that branch (
As I mentioned earlier, time is a major constraint on me here, so this is going to be a future task with no promise of timeline.