Make WordPress Core

Opened 4 years ago

Last modified 4 years ago

#49077 reopened enhancement

Add to Packagist

Reported by: clarinetlord's profile clarinetlord Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:


Currently, the WordPress Develop repo is not on Packagist, even though it now has a composer.json file (thanks to #43558). In order to use as a dependency, for example to use as a foundation to building an automated testing suite for a theme or plugin, you need to manually add the Github URL as an additional repository definition in your project's composer.json file. Normally this wouldn't be much of an issue, but due to the large number of branches and tags, Composer has to search the entire repo to generate a list of tags and branches available on every install/update, which takes several minutes! Adding WordPress Develop to Packagist (to be alongside, would parse and cache branches and tags as they are released via the Packagist Github hook.

Change History (7)

#1 @johnbillion
4 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Thanks for the report @clarinetlord , sorry you didn't get a more timely response.

Can you open a ticket on for this please? Cheers!

#2 @clarinetlord
4 years ago

Thanks @johnbillion. Here the copied ticket in Meta for anyone following this ticket:

#3 @clarinetlord
4 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

Hi @johnbillion, @dd32 on the Meta Trac sent me back here.... Do you know who actually has access to the Packagist WordPress vendor name? @DrewAPicture, since you are a maintainer of, can you shed any light on this?

#4 @desrosj
4 years ago

  • Milestone set to Awaiting Review

I believe any organization administrator on GitHub can do this, which I can coordinate.

Let's just make sure the right process is followed. For example, we don't want tests to be included here. That may mean that is the repo we want listed on Packagist, but that repo does not contain a composer.json file.

Was chatting about this with @johnbillion and he is going to try and locate some past discussions as there were a few arguments against this.

#5 @clarinetlord
4 years ago

Thanks @desrosj for following up with this. However, this ticket is specifically about putting the WordPress Core repo on Packagist, not the WordPress releases repo. I'm fine if someone wants to put both on Packagist, but is already a great Packagist mirror of the WordPress releases that's the de-facto standard right now for including WordPress as a Composer dependency.

#6 @johnbillion
4 years ago

What's your use case @clarinetlord ? Do you need this for the test suite?

If so, I think the test suite should go into its own repo. There's already an unofficial package for this at wp-phpunit/wp-phpunit but I would support adding an official one too.

#7 @clarinetlord
4 years ago

Yes, @johnbillion, I use this primarily for the test suite. I actually wasn't aware of that unofficial package, so thanks for that. I will try that in conjunction with johnpbloch/wordpress and see if that could replace my need to include the entirety of Core in my projects. I would also support an official repo for just the test suite, and would be happy to help with that. Are you thinking it would be some kind of automated mirror, similar to wp-phpunit/wp-phpunit, or moving everything to a self-contained Composer dependency required by Core?

Note: See TracTickets for help on using tickets.