diff options
| author |  Dan Fabulich <DanFabulich@gmail.com> | 2016-01-25 19:42:44 +0000 |
|---|---|---|
| committer |  Lukacs Berki <lberki@google.com> | 2016-01-26 13:05:42 +0000 |
| commit | 3c67b16a0af062b282b40347c5e6791e9db633ad (patch) | |
| tree | 7fc2670c73bc5d80a30dd74e61d0a5e40e1d79b3 /site/docs/external.md | |
| parent | a588c3cef5d5924276d7ac75370751b3d84c7174 (diff) | |
Suggest using release tag when running generate_workspace
Apropos issue #776. This hint in the doc would have saved me from filing a bogus bug.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/778
MOS_MIGRATED_REVID=112972220
Diffstat (limited to 'site/docs/external.md')
| -rw-r--r-- | site/docs/external.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/site/docs/external.md b/site/docs/external.md index 14480d9aa3..9f60b8821f 100644 --- a/site/docs/external.md +++ b/site/docs/external.md @@ -52,7 +52,11 @@ at version 1.0 and another include `C` at 2.0. Bazel provides a tool to help generate these expansive `WORKSPACE` files, called `generate_workspace`. This is not included with the binary installer, so you'll need to clone the [GitHub repo](https://github.com/bazelbuild/bazel) to use it. -`cd` to the GitHub clone and run the following to build the tool and see usage: +We recommend using the tag corresponding to your current version of bazel, which +you can check by running `bazel version`. + +`cd` to the GitHub clone, `git checkout` the appropriate tag, and run the +following to build the tool and see usage: ``` bazel run //src/tools/generate_workspace |