From 440b1dfb3d3a60c6f5b65b0fc9b159c09bf82e3e Mon Sep 17 00:00:00 2001 From: Aaron Fenyes Date: Wed, 2 Apr 2025 12:30:55 -0700 Subject: [PATCH] Clarify where `setup-trunk` puts the Trunk binary --- .forgejo/setup-trunk/action.yaml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.forgejo/setup-trunk/action.yaml b/.forgejo/setup-trunk/action.yaml index 5be3c79..6007527 100644 --- a/.forgejo/setup-trunk/action.yaml +++ b/.forgejo/setup-trunk/action.yaml @@ -10,8 +10,13 @@ runs: using: "composite" steps: - run: rustup target add wasm32-unknown-unknown - # Assume we remain in the top-level directory of the checkout: + + # install the Trunk binary to `ci-bin` within the workspace directory, which + # is determined by the `github.workspace` label and reflected in the + # `GITHUB_WORKSPACE` environment variable. then, make the `trunk` command + # available by placing the fully qualified path to `ci-bin` on the + # workflow's search path - run: mkdir -p ci-bin - run: curl --output - --proto '=https' --tlsv1.2 --retry 10 --retry-connrefused --location --silent --show-error --fail 'https://github.com/trunk-rs/trunk/releases/download/v0.21.12/trunk-x86_64-unknown-linux-gnu.tar.gz' | tar --gunzip --extract --file - working-directory: ci-bin - - run: echo "$(pwd)/ci-bin" >> $GITHUB_PATH + - run: echo "${{ github.workspace }}/ci-bin" >> $GITHUB_PATH