summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAnatolii Kmetiuk <anatoliykmetyuk@gmail.com>2019-07-23 18:01:09 +0200
committerLi Haoyi <haoyi.sg@gmail.com>2019-07-24 00:01:09 +0800
commitbf9648c08fc8fc0c50f46ff4147d6bfe7f432bcf (patch)
tree8685d43ed1066bc7f53004c0cd9d1a6bf4f47beb
parentb0e75b017ba3569e4e0ff2cba8cbd29f03188409 (diff)
downloadmill-bf9648c08fc8fc0c50f46ff4147d6bfe7f432bcf.tar.gz
mill-bf9648c08fc8fc0c50f46ff4147d6bfe7f432bcf.tar.bz2
mill-bf9648c08fc8fc0c50f46ff4147d6bfe7f432bcf.zip
Fix the `dev.run` command documentation in README (#655)
-rw-r--r--readme.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/readme.md b/readme.md
index 2e165ab9..339eb9e0 100644
--- a/readme.md
+++ b/readme.md
@@ -63,10 +63,10 @@ To run test suites:
To manually test Mill on a small build, you can use the `scratch` folder:
```bash
-./mill -i dev.run scratch -w show thingy
+./mill -i dev.run scratch -w resolve _
```
-This runs your current checkout of Mill on the trivial build defined in
+This runs the task `resolve _` with your current checkout of Mill on the trivial build defined in
`scratch/build.sc`. You can modify that build file to add additional modules,
files, etc. and see how it behaves.