The following tables list the functionality of the GitHub Actions libraries and
whether or not they are currently supported by local-action
.
Note
Workflow commands
are currently unsupported. Since local-action
only supports
JavaScript/TypeScript actions, it is assumed that they are using the
GitHub Actions Toolkit.
Feature | Supported | Notes |
---|---|---|
exportVariable() |
✅ | |
setSecret() |
✅ | |
addPath() |
✅ | |
getInput() |
✅ | |
getMultilineInput() |
✅ | |
getBooleanInput() |
✅ | |
setOutput() |
✅ | |
setCommandEcho() |
✅ | Setting is not currently in use |
setFailed() |
✅ | |
isDebug() |
✅ | |
debug() |
✅ | |
error() |
✅ | |
warning() |
✅ | |
notice() |
✅ | |
info() |
✅ | |
startGroup() |
✅ | |
endGroup() |
✅ | |
group() |
✅ | |
saveState() |
✅ | State is not currently in use |
getState() |
✅ | State is not currently in use |
getIDToken() |
⛔ | |
summary.* |
✅ | |
toPosixPath() |
✅ | |
toWin32Path() |
✅ | |
toPlatformPath() |
✅ | |
platform.* |
⛔ |
The following packages are under investigation for how to integrate with
local-action
. Make sure to check back later!
Currently, there shouldn't be any need to stub the functionality of the
following packages from the GitHub Actions Toolkit; they should function as
expected when run using local-action
. If you do encounter a scenario where
this doesn't work correctly, please
open an issue!