Clarify where `setup-trunk` puts the Trunk binary
continuous-integration.yaml #14 -Commit
440b1dfb3d
pushed by
Vectornaut
chore: remove now-useless /home/glen/.venv/bin:/home/glen/.elan/bin:/home/glen/.local/share/pnpm:/home/glen/.local/bin:/home/glen/bin:/usr/local/bin:/usr/bin:/bin:/snap/bin checks
continuous-integration.yaml #13 -Commit
0e38a38b57
pushed by
glen
test: try $GITHUB_PATH for updating PATH
continuous-integration.yaml #12 -Commit
5e441d6b11
pushed by
glen
test: check path at end of setup-trunk
continuous-integration.yaml #11 -Commit
80a4acd56a
pushed by
glen
test: check path after setup-trunk
continuous-integration.yaml #10 -Commit
81035270b8
pushed by
glen
test: move `trunk` installation for CI to ci-bin/
continuous-integration.yaml #9 -Commit
4bb0b05635
pushed by
glen
Find the home directory instead of hard-coding it
continuous-integration.yaml #8 -Commit
df2d45816c
pushed by
Vectornaut
Do the Trunk build check as an end-to-end test
continuous-integration.yaml #7 -Commit
992fb76419
pushed by
Vectornaut
Run the examples as tests
continuous-integration.yaml #6 -Commit
0a9d234557
pushed by
Vectornaut
Switch to CircleCI's Rust + Node container image
continuous-integration.yaml #5 -Commit
7f45e98b46
pushed by
Vectornaut
Run CI on a stock image, installing Trunk by hand
continuous-integration.yaml #4 -Commit
4251242953
pushed by
Vectornaut
Tell Docker to build Trunk with only one job
continuous-integration.yaml #3 -Commit
f212cfadf4
pushed by
Vectornaut
Remove the CI image setup script
continuous-integration.yaml #2 -Commit
15375dc932
pushed by
Vectornaut
Fail continuous integration on warnings
continuous-integration.yaml #1 -Commit
71f4cd184c
pushed by
Vectornaut