Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Commit

Permalink
Suggest using release tag when running generate_workspace
Browse files Browse the repository at this point in the history
Apropos issue #776. This hint in the doc would have saved me from filing a bogus bug.

--
Reviewed-on: bazelbuild/bazel#778
MOS_MIGRATED_REVID=112972220
  • Loading branch information
dfabulich authored and lberki committed Jan 26, 2016
1 parent d1dc692 commit 0e9003d
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/external.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 0e9003d

Please sign in to comment.