Go to file
Robert Anderson 251fd685dd Comments: Fix title not updating when replying to a comment
When replying to an existing comment, the comment form is moved to below the
existing comment with JS, but the form heading was not being updated. This
fixes the issue by introducing a new data-attribute to the reply link with the
correct heading string, and applying that string to the heading when the form
is moved.

Props isabel_brison, azaozz, peterwilsoncc.
Fixes #38009.


git-svn-id: https://develop.svn.wordpress.org/trunk@47506 602fd350-edb4-49c9-b593-d223f7449a82
2020-03-25 04:53:06 +00:00
.github General: Introduce a pull request template. 2020-02-21 18:23:28 +00:00
src Comments: Fix title not updating when replying to a comment 2020-03-25 04:53:06 +00:00
tests Docs: Update inline comment in `Tests_DB::test_locale_floats()`. 2020-03-24 01:05:31 +00:00
tools Build Tools: Use the new `combinedOutputFile` setting for the updated DependencyExtractionWebpackPlugin and output `script-loader-packages.php` directly in `wp-includes/assets/`. 2020-03-18 04:48:19 +00:00
.editorconfig
.env
.gitignore Build/Test Tools: Introduce Install-changed. It keeps a hash of `package.json` and compares it when run. If it has any changes, it runs `npm install`. 2020-03-24 01:04:43 +00:00
.jshintrc
.npmrc
.nvmrc
.travis.yml Tests: Use `PUPPETEER_SKIP_CHROMIUM_DOWNLOAD` environment variable instead of config setting. 2020-03-16 12:23:01 +00:00
Gruntfile.js Build/Test Tools: Introduce Install-changed. It keeps a hash of `package.json` and compares it when run. If it has any changes, it runs `npm install`. 2020-03-24 01:04:43 +00:00
README.md
SECURITY.md Trunk is now 5.5 alpha 2020-03-04 01:18:56 +00:00
appveyor.yml
composer.json Coding Standards: Update PHPCS Composer plugin to v0.6.0. 2020-02-28 01:38:58 +00:00
composer.lock
docker-compose.yml Build/Test Tools: Expose port 3306 of MySQL container. 2020-02-09 21:20:25 +00:00
jsdoc.conf.json
package-lock.json Build/Test Tools: Introduce Install-changed. It keeps a hash of `package.json` and compares it when run. If it has any changes, it runs `npm install`. 2020-03-24 01:04:43 +00:00
package.json Build/Test Tools: Introduce Install-changed. It keeps a hash of `package.json` and compares it when run. If it has any changes, it runs `npm install`. 2020-03-24 01:04:43 +00:00
phpcompat.xml.dist
phpcs.xml.dist Coding Standards: Adjust coding standards to always omit parentheses for `include`/`require` statements. 2020-02-07 19:14:29 +00:00
phpunit.xml.dist
webpack.config.js
wp-cli.yml
wp-config-sample.php
wp-tests-config-sample.php Tests: Revert the `dirname( __FILE__ )` replacement in `wp-tests-config-sample.php` for now, to avoid breaking unit tests created with WP-CLI `scaffold` command. 2020-02-06 21:49:13 +00:00

README.md

WordPress

Build Status

Welcome to the WordPress development repository! Please check out our contributor handbook for information about how to open bug reports, contribute patches, test, documentation, or get involved in any way you can.

Getting Started

WordPress is a PHP/MySQL-based project. We have a basic development environment that you can quickly get up and running with a few commands. First off, you will need to download and install Docker, if you don't have it already. After that, there are a few commands to run:

Development Environment Commands

Running these commands will start the development environment:

npm install
npm run build:dev
npm run env:start
npm run env:install

Additionally, npm run env:stop will stop the environment.

npm run env:cli runs the WP-CLI tool. WP-CLI has a lot of useful commands you can use to work on your WordPress site. Where the documentation mentions running wp, run npm run env:cli instead. For example, npm run env:cli help.

npm run test:php and npm run test:e2e run the PHP and E2E test suites, respectively.