Configure the repository for development mode by removing packed libraries, adding tokens, preparing sources, and closing LabVIEW.
Common parameters are described in Common parameters.
string
): Path relative to the action’s working directory. Use “.” when the working directory is desired.None.
GitHub Action inputs are provided in snake_case
, while CLI parameters use PascalCase
. The table below maps each input to its corresponding CLI parameter. For details on shared CLI flags, see Common parameters.
Input | CLI parameter | Description |
---|---|---|
relative_path |
RelativePath |
Path relative to the working directory. Use ‘.’ to refer to the working directory. |
gcli_path |
gcliPath |
Optional path to the g-cli executable. |
working_directory |
WorkingDirectory |
Base directory for the action; relative paths are resolved from here. |
log_level |
LogLevel |
Verbosity level (ERROR|WARN|INFO|DEBUG). |
dry_run |
DryRun |
If true, simulate the action without side effects. |
pwsh -File actions/Invoke-OSAction.ps1 -ActionName set-development-mode -ArgsJson '{
"WorkingDirectory": ".",
"RelativePath": "."
}'
- name: Set development mode
uses: LabVIEW-Community-CI-CD/open-source/set-development-mode@v1
with:
working_directory: '.'
relative_path: '.'
0
– development mode enabledFor troubleshooting tips, see the troubleshooting guide.