The user may wish to run compilation tests on sketches bundled with installed library dependencies. These are installed to /home/github/Arduino/libraries, which is outside the working directory of the action's Docker container.
Use cases:
Checking impact of changes on libraries that have the library under test as a dependency.
Checking impact of changes to the platform under test on external libraries.
This required:
Fixing a bug with the code used to provide user-friendly relative paths in log and report output that made it incompatible with paths outside the working directory provided by the user via the sketch-paths input.
Adding support for ~ in input paths. This allows users to use the familiar universal default user directory (sketchbook) path location (~/Arduino) instead of needing to remember that HOME in the docker container is /github/home.
Documenting that the libraries are installed under ~/Arduino/libraries
The user may wish to run compilation tests on sketches bundled with installed library dependencies. These are installed to
/home/github/Arduino/libraries
, which is outside the working directory of the action's Docker container.Use cases:
This required:
sketch-paths
input.~
in input paths. This allows users to use the familiar universal default user directory (sketchbook) path location (~/Arduino
) instead of needing to remember thatHOME
in the docker container is/github/home
.~/Arduino/libraries