Skip to content

Commit 07634cc

Browse files
authored
docs: Fix broken doc links (#3931)
1 parent d84cc49 commit 07634cc

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

.gitattributes

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
**/cargo-bazel-lock.json linguist-generated
33
crate_universe/3rdparty/crates/** linguist-generated
44
crate_universe/test_data/metadata/*/metadata.json linguist-generated
5-
examples/bzlmod/hello_world/third-party/crates/** linguist-generated
5+
examples/hello_world/third-party/crates/** linguist-generated
66
examples/crate_universe_unnamed/vendor_remote_manifests/crates/** linguist-generated
77
examples/crate_universe_unnamed/vendor_remote_pkgs/crates/** linguist-generated
88
examples/crate_universe/vendor_external/crates/** linguist-generated

crate_universe/extensions.bzl

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ For more details about repin, [please refer to the documentation](https://bazelb
144144
In cases where Rust targets have heavy interactions with other Bazel targets ([Cc](https://docs.bazel.build/versions/main/be/c-cpp.html), [Proto](https://rules-proto-grpc.com/en/4.5.0/lang/rust.html),
145145
etc.), maintaining Cargo.toml files may have diminishing returns as things like rust-analyzer
146146
begin to be confused about missing targets or environment variables defined only in Bazel.
147-
In situations like this, it may be desirable to have a "Cargo free" setup. You find an example in the in the [example folder](https://github.com/bazelbuild/rules_rust/examples/bzlmod/hello_world_no_cargo).
147+
In situations like this, it may be desirable to have a "Cargo free" setup. You find an example in the in the [example folder](https://github.com/bazelbuild/rules_rust/tree/main/examples/hello_world_no_cargo).
148148
149149
crates_repository supports this through the packages attribute,
150150
as shown below.
@@ -227,7 +227,7 @@ Only a cargo workspace needs updating whenever the underlying Cargo.toml file ch
227227
In some cases, it is require that all external dependencies are vendored, meaning downloaded
228228
and stored in the workspace. This helps, for example, to conduct licence scans, apply custom patches,
229229
or to ensure full build reproducibility since no download error could possibly occur.
230-
You find a complete example in the in the [example folder](https://github.com/bazelbuild/rules_rust/examples/bzlmod/all_deps_vendor).
230+
You find a complete example in the in the [example folder](https://github.com/bazelbuild/rules_rust/tree/main/examples/all_deps_vendor).
231231
232232
For the setup, you need to add the skylib in addition to the rust rules to your `MODULE.bazel`.
233233
@@ -367,7 +367,7 @@ sys_deps()
367367
368368
Now, you can build the project as usual.
369369
370-
There are some more examples of using crate_universe with bzlmod in the [example folder](https://github.com/bazelbuild/rules_rust/blob/main/examples/bzlmod/).
370+
There are some more examples of using crate_universe with bzlmod in the [example folder](https://github.com/bazelbuild/rules_rust/blob/main/examples/).
371371
372372
"""
373373

0 commit comments

Comments
 (0)