[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-8533":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":25,"readmeContent":26,"aiSummary":27,"trendingCount":16,"starSnapshotCount":16,"syncStatus":28,"lastSyncTime":29,"discoverSource":30},8533,"wordpress-develop","WordPress\u002Fwordpress-develop","WordPress","WordPress Develop, Git-ified. Synced from git:\u002F\u002Fdevelop.git.wordpress.org\u002F, including branches and tags! This repository is just a mirror of the WordPress subversion repository. Please include a link to a pre-existing ticket on https:\u002F\u002Fcore.trac.wordpress.org\u002F with every pull request.","https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002Fhandbook\u002Fcontribute\u002Fgit\u002Fgithub-pull-requests-for-code-review\u002F",null,"PHP",3349,3504,144,2760,0,5,29,1,67.4,"GNU General Public License v2.0",false,"trunk",[],"2026-06-12 04:00:40","# WordPress\n\nWelcome to the WordPress development repository! Please check out the [contributor handbook](https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002Fhandbook\u002F) for information about how to open bug reports, contribute patches, test changes, write documentation, or get involved in any way you can.\n\n* [Getting Started](#getting-started)\n* [Credentials](#credentials)\n\n## Getting Started\n\n### Local development\n\nWordPress is a PHP, MySQL, and JavaScript based project, and uses Node for its JavaScript dependencies. A local development environment is available to quickly get up and running.\n\nYou will need a basic understanding of how to use the command line on your computer. This will allow you to set up the local development environment, to start it and stop it when necessary, and to run the tests.\n\nYou will need Node and npm installed on your computer. Node is a JavaScript runtime used for developer tooling, and npm is the package manager included with Node. If you have a package manager installed for your operating system, setup can be as straightforward as:\n\n* macOS: `brew install node`\n* Windows: `choco install nodejs`\n* Ubuntu: `apt install nodejs npm`\n\nIf you are not using a package manager, see the [Node.js download page](https:\u002F\u002Fnodejs.org\u002Fen\u002Fdownload\u002F) for installers and binaries.\n\n**Note:** WordPress currently only officially supports Node.js `20.x` and npm `10.x`.\n\nYou will also need a container environment such as [Docker Desktop](https:\u002F\u002Fwww.docker.com\u002Fproducts\u002Fdocker-desktop) installed and running on your computer. The container environment is the virtualization software that powers the local development environment and can be installed just like any other regular application.\n\n**Note:** WordPress currently only officially supports Docker but several container environments are available and should generally be compatible, such as [Colima](https:\u002F\u002Fgithub.com\u002Fabiosoft\u002Fcolima), [OrbStack](https:\u002F\u002Forbstack.dev\u002F), [Podman Desktop](https:\u002F\u002Fpodman-desktop.io\u002F), and [Rancher Desktop](https:\u002F\u002Francherdesktop.io\u002F).\n\n### Development Environment Commands\n\nEnsure your container environment is running before using these commands.\n\n#### To start the development environment for the first time\n\nYou can get started using the local development environment with these steps:\n\n1. Go to https:\u002F\u002Fgithub.com\u002FWordPress\u002Fwordpress-develop and fork the repository to your own GitHub account. \n1. Then clone the forked repository to your computer using `git clone https:\u002F\u002Fgithub.com\u002F\u003Cyour-username>\u002Fwordpress-develop.git`.\n1. Navigate into the directory for the cloned repository using `cd wordpress-develop`.\n1. Add the origin repo as an `upstream` remote via `git remote add upstream https:\u002F\u002Fgithub.com\u002FWordPress\u002Fwordpress-develop.git`.\n1. Then you can keep your branches up to date via `git pull --ff upstream\u002Ftrunk`, for example.\n\nAlternatively, if you have the [GitHub CLI](https:\u002F\u002Fcli.github.com\u002F) installed, you can simply run `gh repo fork WordPress\u002Fwordpress-develop --clone --remote` ([docs](https:\u002F\u002Fcli.github.com\u002Fmanual\u002Fgh_repo_fork)). This command will:\n1. Fork the repository to your account (use the `--org` flag to clone into an organization).\n1. Clone the repository to your machine. \n1. Add `WordPress\u002Fwordpress-develop` as `upstream` and set it to the default `remote` repository\n\nAfter this, remember to run `cd wordpress-develop`.\n\nOnce you have forked and cloned the repository to your computer, run the following commands in a terminal:\n\n```\nnpm install\nnpm run build:dev\nnpm run env:start\nnpm run env:install\n```\n\nYour WordPress site will be accessible at http:\u002F\u002Flocalhost:8889. You can see or change configurations in the `.env` file located at the root of the project directory.\n\n#### To watch for changes\n\nIf you're making changes to WordPress core files, you should start the file watcher in order to build or copy the files as necessary:\n\n```\nnpm run dev\n```\n\nTo stop the watcher, press `ctrl+c`.\n\n#### To run a [WP-CLI](https:\u002F\u002Fmake.wordpress.org\u002Fcli\u002Fhandbook\u002F) command\n\n```\nnpm run env:cli -- \u003Ccommand>\n```\n\nWP-CLI has [many useful commands](https:\u002F\u002Fdeveloper.wordpress.org\u002Fcli\u002Fcommands\u002F) you can use to work on your WordPress site. Where the documentation mentions running `wp`, run `npm run env:cli --` instead. For example:\n\n```\nnpm run env:cli -- help\n```\n\n#### To run the tests\n\nThese commands run the PHP and end-to-end test suites, respectively:\n\n```\nnpm run test:php\nnpm run test:e2e\n```\n\nYou can pass extra parameters into the PHP tests by adding `--` and then the [command-line options](https:\u002F\u002Fdocs.phpunit.de\u002Fen\u002F10.4\u002Ftextui.html#command-line-options):\n\n```\nnpm run test:php -- --filter \u003Ctest name>\nnpm run test:php -- --group \u003Cgroup name or ticket number>\n```\n\n#### To lint the workflow files\n\nGitHub Actions workflows operate in a privileged software supply chain environment, therefore all workflow files must adhere to a high degree of quality and security standards.\n\nAll YAML workflow files within the `.github\u002Fworkflows` directory are statically scanned when modified using [Actionlint](https:\u002F\u002Fgithub.com\u002Frhysd\u002Factionlint) and [Zizmor](https:\u002F\u002Fgithub.com\u002Fzizmorcore\u002Fzizmor). It's recommended that you install both of these tools locally using a package manager to run prior to submitting changes to workflow files.\n\n- [Actionlint installations instructions](https:\u002F\u002Fgithub.com\u002Frhysd\u002Factionlint\u002Fblob\u002Fmain\u002Fdocs\u002Finstall.md)\n- [Zizmor installation instructions](https:\u002F\u002Fdocs.zizmor.sh\u002Finstallation\u002F)\n\nTo run Actionlint:\n\n```\nactionlint\n```\n\nTo run Zizmor for all workflow files (note the trailing period):\n\n```\nzizmor .\n```\n\n**Note:** A workflow run failure will not occur when issues are detected by Zizmor. Instead, the generated report is submitted to GitHub Code Scanning and surfaced through a status check. Some locally reported issues may be ignored based on the repository's configured Code Scanning settings.\n\n#### Generating a code coverage report\nPHP code coverage reports are [generated daily](https:\u002F\u002Fgithub.com\u002FWordPress\u002Fwordpress-develop\u002Factions\u002Fworkflows\u002Ftest-coverage.yml) and [submitted to Codecov.io](https:\u002F\u002Fapp.codecov.io\u002Fgh\u002FWordPress\u002Fwordpress-develop).\n\nAfter the local container environment has [been installed and started](#to-start-the-development-environment-for-the-first-time), the following command can be used to generate a code coverage report. \n\n```\nnpm run test:coverage\n```\n\nThe command will generate three coverage reports in HTML, PHP, and text formats, saving them in the `coverage` folder.\n\n**Note:** xDebug is required to generate a code coverage report, which can slow down PHPUnit significantly. Passing selection-based options such as `--group` or `--filter` can decrease the overall time required but will result in an incomplete report.\n\n#### To restart the development environment\n\nYou may want to restart the environment if you've made changes to the configuration in the `docker-compose.yml` or `.env` files. Restart the environment with:\n\n```\nnpm run env:restart\n```\n\n#### To stop the development environment\n\nYou can stop the environment when you're not using it to preserve your computer's power and resources:\n\n```\nnpm run env:stop\n```\n\n#### To start the development environment again\n\nStarting the environment again is a single command:\n\n```\nnpm run env:start\n```\n\n#### Resetting the development environment\n\nThe development environment can be reset. This will destroy the database and attempt to remove the pulled container images.\n\n```\nnpm run env:reset\n```\n\n### Apple Silicon machines and old MySQL\u002FMariaDB versions\n\nOlder MySQL and MariaDB container images do not support Apple Silicon processors (M1, M2, etc.). This is true for:\n\n- MySQL versions 5.7 and earlier\n- MariaDB 5.5\n\nWhen using these versions on an Apple Silicon machine, you must create a `docker-compose.override.yml` file with the following contents:\n\n```\nservices:\n\n  mysql:\n    platform: linux\u002Famd64\n```\n\nAdditionally, the \"Use Rosetta for x86\u002FAMD64 emulation on Apple Silicon\" setting in your container environment (if applicable) needs to be disabled for this workaround.\n\n## Credentials\n\nThese are the default environment credentials:\n\n* Database Name: `wordpress_develop`\n* Username: `root`\n* Password: `password`\n\nTo login to the site, navigate to http:\u002F\u002Flocalhost:8889\u002Fwp-admin.\n\n* Username: `admin`\n* Password: `password`\n\n**Note:** With Codespaces, open the portforwarded URL from the ports tab in the terminal, and append `\u002Fwp-admin` to login to the site.\n\nTo generate a new password (recommended):\n\n1. Go to the Dashboard\n2. Click the Users menu on the left\n3. Click the Edit link below the admin user\n4. Scroll down and click 'Generate password'. Either use this password (recommended) or change it, then click 'Update User'. If you use the generated password be sure to save it somewhere (password manager, etc).\n","WordPress\u002Fwordpress-develop项目是用于开发和贡献WordPress核心代码的Git版本库。它同步自官方的Subversion仓库，包含了所有分支和标签，为开发者提供了一个基于Git的工作环境。项目主要使用PHP、MySQL以及JavaScript，并且依赖Node.js进行JavaScript包管理，同时需要Docker等容器环境来搭建本地开发环境。此项目非常适合希望参与WordPress开源社区、贡献代码或修复bug的开发者，同时也适用于想要深入了解WordPress内部工作原理的技术爱好者。通过遵循项目提供的贡献指南，任何人都可以轻松地开始本地开发并提交自己的改动。",2,"2026-06-11 03:18:29","top_language"]