Update doc references to release-operator folder

hannobraun · Apr 13, 2022 · d2cedca · d2cedca
1 parent c687f18
commit d2cedca
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/RELEASES.md b/RELEASES.md
@@ -47,7 +47,7 @@ In the release branch, update the version numbers in the `Cargo.toml` files of a
 
 Push the release branch and create a pull request and label it as `release`. Once the CI build completed successfully, merge the pull-request and mention the new version in the commit, e.g. `Release v0.1.2`.
 
-The [release-operator](./release-operator) will run in the scope of GitHub Actions' [CD](./.github/workflows/cd.yml) workflow. It will yield a set of compiled binaries, their checksums and a new GitHub Release with all artifacts attached.
+The [release-operator](./tools/release-operator) will run in the scope of GitHub Actions' [CD](./.github/workflows/cd.yml) workflow. It will yield a set of compiled binaries, their checksums and a new GitHub Release with all artifacts attached.
 
 Next, publish the release by running `cargo publish` for each crate.
 

diff --git a/tools/release-operator/README.md b/tools/release-operator/README.md
@@ -55,7 +55,7 @@ As seen above, the release operator requires the maintainer to:
 ### Detect a Release
 
 ```shell
-# release-operator/
+# tools/release-operator/
 cargo run -- detect --sha <commit-sha> --label <release-label>
 ```
 
@@ -113,7 +113,7 @@ The release operator defines "outputs" which can be read by subsequent steps wit
 ### Publish a List of Crates
 
 ```shell
-# release-operator/
+# tools/release-operator/
 cargo run -- publish \
   --token <crates.io-token> \
   --crate ../fj \