@@ -88,9 +88,11 @@ Usage: bazel-diff generate-hashes [-hkvV] -b=<bazelPath> [-s=<seedFilepaths>]
8888Writes to a file the SHA256 hashes for each Bazel Target in the provided
8989workspace.
9090 <outputPath> The filepath to write the resulting JSON of
91- dictionary target => SHA-256 values
91+ dictionary target => SHA-256 values. If not
92+ specified, the JSON will be written to STDOUT.
9293 -b, --bazelPath=<bazelPath>
93- Path to Bazel binary
94+ Path to Bazel binary. If not specified, the Bazel
95+ binary available in PATH will be used.
9496 -co, --bazelCommandOptions=<bazelCommandOptions>
9597 Additional space separated Bazel command options used
9698 when invoking Bazel
@@ -99,6 +101,16 @@ workspace.
99101 relative file path from workspace path to its
100102 content hash. Files in this map will skip content
101103 hashing and use provided value
104+ --fineGrainedHashExternalRepos=<fineGrainedHashExternalRepos>
105+ Comma separate list of external repos in which
106+ fine-grained hashes are computed for the targets.
107+ By default, external repos are treated as an opaque
108+ blob. If an external repo is specified here,
109+ bazel-diff instead computes the hash for individual
110+ targets. For example, one wants to specify `maven`
111+ here if they user rules_jvm_external so that
112+ individual third party dependency change won't
113+ invalidate all targets in the mono repo.
102114 -h, --help Show this help message and exit.
103115 -k, --[no-]keep_going This flag controls if `bazel query` will be executed
104116 with the `--keep_going` flag or not. Disabling this
0 commit comments