wordpress/wordpress-develop

WordPress Develop, Git-ified. Synced from git://develop.git.wordpress.org/, including branches and tags! This repository is just a mirror of the WordPress...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Type:Server / PlatformCategory(s):CMS, Static Sites & ForumsWeb Development
Added to GitGenius on September 20th, 2026
Created on December 5th, 2016
Open Issues & Pull Requests: 3,495 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3,687
Total Stargazers: 3,446 (+0)
Total Subscribers: 142 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

WordPress Develop is a Git mirror of the WordPress core subversion repository that serves as the official development environment for WordPress contributors.

The project addresses the need for a modern Git-based workflow to contribute to WordPress core, which traditionally used Subversion. It provides a containerized local development environment that allows contributors to set up, test, and submit changes to the WordPress codebase. The environment is built on PHP, MySQL, and JavaScript, with Node.js used for managing JavaScript dependencies. Contributors work by forking the repository, cloning it locally, and submitting pull requests linked to tickets on the core issue tracker.

This repository is essential for anyone contributing to WordPress core itself rather than building plugins or themes. It suits developers who want to fix bugs, add features, or improve WordPress at the foundation level. The project requires familiarity with command-line tools and expects contributors to maintain a local development environment using Docker or compatible container software. The README emphasizes that all pull requests must reference an existing ticket on the core issue tracker, establishing a structured contribution process tied to the official bug and feature tracking system.

Development activity shows consistent engagement with the contribution workflow. The project maintains active synchronization with the upstream Subversion repository, ensuring the Git mirror stays current. Contributors regularly submit pull requests that are reviewed against core tickets, indicating ongoing participation in the development cycle. The project documentation directs contributors to the core handbook for detailed guidance on reporting bugs, writing patches, testing changes, and other contribution methods, reflecting an established and documented development process.