Skip to content

Commit f2bd770

Browse files
authored
Fix pre-commit hooks after 378b806 (TraceMachina#482)
Also fix some remaining `native-link` occurrences.
1 parent 449376b commit f2bd770

File tree

8 files changed

+90
-90
lines changed

8 files changed

+90
-90
lines changed

nativelink-docs/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# NativeLink Docs
1+
# NativeLink Docs
22

33
### Development
44

nativelink-docs/contributing.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ efforts from contributors on the same issue.
5252

5353
- Add tests relevant to the fixed bug or new feature.
5454

55-
- Unit-tests run with `bazel test //..` must pass locally.
55+
- Unit-tests run with `bazel test //..` must pass locally.
5656

5757
<Note>See Quickstart if having trouble running unit tests.</Note>
5858

nativelink-docs/introduction.mdx

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ description: 'What is NativeLink?'
1616

1717
Native link is an extremely (blazingly?) fast and efficient build cache and
1818
remote executor for systems that communicate using the [Remote execution
19-
protocol](https://github.com/bazelbuild/remote-apis/blob/main/build/bazel/remote/execution/v2/remote_execution.proto)
20-
such as [Bazel](https://bazel.build), [Buck2](https://buck2.build),
19+
protocol](https://github.com/bazelbuild/remote-apis/blob/main/build/bazel/remote/execution/v2/remote_execution.proto)
20+
such as [Bazel](https://bazel.build), [Buck2](https://buck2.build),
2121
[Goma](https://chromium.googlesource.com/infra/goma/client/) and
2222
[Reclient](https://github.com/bazelbuild/reclient).
2323

nativelink-docs/logo/dark.svg

+5-5
Loading

nativelink-docs/logo/light.svg

+65-65
Loading

nativelink-docs/mint.json

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@
4747
}
4848
],
4949
"footerSocials": {
50-
"github": "https://github.com/TraceMachina/native-link",
50+
"github": "https://github.com/TraceMachina/nativelink",
5151
"website": "https://tracemachina.com/",
5252
"twitter": "https://twitter.com/tracemachina"
5353
}

nativelink-docs/package-lock.json

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

nativelink-docs/quickstart.mdx

+14-14
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ bazel --version
4040
```
4141

4242
```shell Docker-ARM
43-
docker run -it --name=NL -v $(pwd):/native-link ubuntu:latest
43+
docker run -it --name=NL -v $(pwd):/nativelink ubuntu:latest
4444

4545
# If above has already been run or trying to start in new terminal:
4646
docker exec -it NL bash
@@ -64,7 +64,7 @@ bazel --version
6464
```
6565

6666
```shell Docker-x86
67-
docker run -it --name=NL -v $(pwd):/native-link ubuntu:latest
67+
docker run -it --name=NL -v $(pwd):/nativelink ubuntu:latest
6868

6969
# If above has already been run or trying to start in new terminal:
7070
docker exec -it NL bash
@@ -104,7 +104,7 @@ bazel --version
104104
### Compile and Run NativeLink Server
105105

106106
The following command will allow you to compile and run the NativeLink server for the first time.
107-
107+
108108
```shell
109109
apt install -y gcc g++ lld python3
110110
# Install cargo (if needed).
@@ -113,17 +113,17 @@ The following command will allow you to compile and run the NativeLink server fo
113113

114114
# Run with Cargo:
115115
# Unoptimized development build
116-
cargo run --bin cas -- ./native-link-config/examples/basic_cas.json
116+
cargo run --bin cas -- ./nativelink-config/examples/basic_cas.json
117117

118118
# Optimized release build
119-
cargo run --release --bin cas -- ./native-link-config/examples/basic_cas.json
119+
cargo run --release --bin cas -- ./nativelink-config/examples/basic_cas.json
120120

121121
# Run with Bazel:
122122
# Unoptimized development build on Unix.
123-
bazel run cas -- ./native-link-config/examples/basic_cas.json
123+
bazel run cas -- ./nativelink-config/examples/basic_cas.json
124124

125125
# Optimized release build on Unix.
126-
bazel run -c opt cas -- ./native-link-config/examples/basic_cas.json
126+
bazel run -c opt cas -- ./nativelink-config/examples/basic_cas.json
127127
```
128128

129129
<Note>The `--release` flag causes link-time-optmization to be enabled, which can take a while to compile, but will result in a much faster binary.</Note>
@@ -138,7 +138,7 @@ bazel test //... \
138138
--remote_executor=grpc://127.0.0.1:50051 \
139139
--remote_default_exec_properties=cpu_count=1
140140

141-
# This causes bazel to run the commands through an all-in-one `CAS`, `scheduler`
141+
# This causes bazel to run the commands through an all-in-one `CAS`, `scheduler`
142142
# and `worker`.
143143
```
144144
<Note>If the NativeLink server was run in a docker container, the above command for starting the NativeLink client will need to be run in the same container as the server in order to connect.</Note>
@@ -217,10 +217,10 @@ cosign verify ghcr.io/tracemachina/nativelink:${PINNED_TAG} \
217217
--certificate-oidc-issuer=https://token.actions.githubusercontent.com
218218
```
219219
220-
<Tip>
221-
The images are reproducible on `X86_64-unknown-linux-gnu`. If you're on
222-
such a system you can produce a binary-identical image by building the
223-
`.#image` flake output locally. Make sure that your `git status` is
224-
completely clean and aligned with the commit you want to reproduce.
225-
Otherwise the image will be tainted with a `"dirty"` revision label.
220+
<Tip>
221+
The images are reproducible on `X86_64-unknown-linux-gnu`. If you're on
222+
such a system you can produce a binary-identical image by building the
223+
`.#image` flake output locally. Make sure that your `git status` is
224+
completely clean and aligned with the commit you want to reproduce.
225+
Otherwise the image will be tainted with a `"dirty"` revision label.
226226
</Tip>

0 commit comments

Comments
 (0)