Skip to content

Commit f9ef481

Browse files
committed
remove non-portable utils/dev-build
closes #995
1 parent 7bd265d commit f9ef481

2 files changed

Lines changed: 15 additions & 12 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,24 @@
11
Contribute
22
==========
33

4+
Setting up
5+
----------
6+
7+
1. Clone this git repository on your local machine.
8+
2. Install [Composer](https://getcomposer.org/) if you don't already have it.
9+
2. Run `composer install` to fetch all the dependencies.
10+
3. Run `./bin/wp --info` to test if everything was installed properly.
11+
4. Download PHPUnit: `curl -L https://phar.phpunit.de/phpunit.phar > phpunit.phar`
12+
5. Download Behat: `curl -L http://behat.org/downloads/behat.phar > behat.phar`
13+
14+
Submitting patches
15+
------------------
16+
417
Whether you want to fix a bug or implement a new feature, the process is pretty much the same:
518

619
0. [Search existing issues](https://github.com/wp-cli/wp-cli/issues); if you can't find anything related to what you want to work on, open a new issue so that you can get some initial feedback.
720
1. [Fork](https://github.com/wp-cli/wp-cli/fork) the repository.
8-
2. Make the code changes in your fork.
21+
2. Push the code changes from your local clone to your fork.
922
3. Open a pull request.
1023

1124
It doesn't matter if the code isn't perfect. The idea is to get it reviewed early and iterate on it.
@@ -22,12 +35,6 @@ There are two types of automated tests:
2235
* unit tests, implemented using [PHPUnit](http://phpunit.de/)
2336
* functional tests, implemented using [Behat](http://behat.org)
2437

25-
To set everything up, just run:
26-
27-
```bash
28-
./utils/dev-build
29-
```
30-
3138
### Unit tests
3239

3340
The unit test files are in the `tests/` directory.

‎README.md‎

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Installing
99
------------
1010
If you just want to use WP-CLI, see <http://wp-cli.org/#install>.
1111

12-
If you want to hack on WP-CLI, then clone this repository and run `./utils/dev-build`.
12+
If you want to hack on WP-CLI, see [CONTRIBUTING.md](CONTRIBUTING.md).
1313

1414
Where can I get more info?
1515
--------------------------
@@ -25,10 +25,6 @@ To suggest a feature, report a bug, or general discussion, visit the [issues sec
2525

2626
If you're reporting a bug, please also post the output from `wp --info`.
2727

28-
How can I help?
29-
---------------
30-
See [CONTRIBUTING.md](CONTRIBUTING.md).
31-
3228
Credits
3329
-------
3430
Besides the libraries defined in [composer.json](composer.json), we have used code or ideas from the following projects:

0 commit comments

Comments
 (0)