Bug 1275774 - Fix taskcluster how-to docs example command r=dustin
authorBrian Stack <bstack@mozilla.com>
Fri, 16 Sep 2016 13:46:03 -0700
changeset 315542 d596d23a7efe561c6fed90466d488d5a36fbc839
parent 315541 409769321b119013afc6fd41345605f4a188bcf3
child 315543 5202c23288507d490509e97a51c44856ca809e94
push id30751
push usercbook@mozilla.com
push dateThu, 29 Sep 2016 09:43:23 +0000
treeherdermozilla-central@b67dc49095dc [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdustin
bugs1275774
milestone52.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1275774 - Fix taskcluster how-to docs example command r=dustin MozReview-Commit-ID: 8gFeRHeSRd8
taskcluster/docs/how-tos.rst
--- a/taskcluster/docs/how-tos.rst
+++ b/taskcluster/docs/how-tos.rst
@@ -37,17 +37,17 @@ 1. Find a recent decision task on the pr
    contents are simple enough if you would like to modify it, and it is
    documented in :doc:`parameters`.
 
 2. Run one of the ``mach taskgraph`` subcommands (see :doc:`taskgraph`) to
    generate a baseline against which to measure your changes.  For example:
 
    .. code-block:: none
 
-       ./mach taskgraph --json -p parameters.yml tasks > old-tasks.json
+       ./mach taskgraph tasks --json -p parameters.yml > old-tasks.json
 
 3. Make your modifications under ``taskcluster/``.
 
 4. Run the same ``mach taskgraph`` command, sending the output to a new file,
    and use ``diff`` to compare the old and new files.  Make sure your changes
    have the desired effect and no undesirable side-effects.
 
 5. When you are satisfied with the changes, push them to try to ensure that the