Making WordPress.org

Opened 3 years ago

Last modified 3 years ago

#5393 new enhancement

Add https://github.com/WordPress/wordpress-develop to Packagist

Reported by: clarinetlord's profile clarinetlord Owned by:
Milestone: Priority: normal
Component: Version Control Keywords:
Cc:

Description

Transferred from: https://core.trac.wordpress.org/ticket/49077
Currently, the WordPress Develop repo is not on Packagist, even though it now has a composer.json file (thanks to https://core.trac.wordpress.org/ticket/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 https://packagist.org/packages/wordpress/phpdoc-parser), would parse and cache branches and tags as they are released via the Packagist Github hook.

Change History (1)

#1 @dd32
3 years ago

Hi @clarinetlord,

While the WordPress Meta team manages the infrastructure, we're not the best team to do this, instead, I'd probably redirect you back to the Core Team to figure it out - even though they sent you here https://core.trac.wordpress.org/ticket/49077.

Note: See TracTickets for help on using tickets.