While migrating to it, an unexpected sbt: not found error was noticed if a checkout step is run after the setup-sbt.
This github workflow should reproduce the issue:
The Check sbt step fails with sbt: not found error for me.
Which is not the case e.g. for setup-java - you can call java afterwards.
A quick glance showed that setup-sbt creates a directory to unpack sbt to in the working directory of the workflow. checkout on the other hand cleans the working directory.
What do you think about creating a directory for sbt somewhere outside of the working directory?
Hi, thanks a lot for the action!
While migrating to it, an unexpected
sbt: not found
error was noticed if acheckout
step is run after thesetup-sbt
. This github workflow should reproduce the issue:The
Check sbt
step fails withsbt: not found
error for me. Which is not the case e.g. forsetup-java
- you can calljava
afterwards. A quick glance showed thatsetup-sbt
creates a directory to unpack sbt to in the working directory of the workflow.checkout
on the other hand cleans the working directory.What do you think about creating a directory for
sbt
somewhere outside of the working directory?