Check that all files in a LabVIEW project are present by scanning for items missing from the .lvproj
.
Common parameters are described in Common parameters.
string
): LabVIEW version used to open the project.string
): “32” or “64” bitness of LabVIEW.string
): Path to the project file to inspect.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 |
---|---|---|
lv_version |
LVVersion |
LabVIEW version to use. |
supported_bitness |
SupportedBitness |
Target LabVIEW bitness (32 or 64). |
project_file |
ProjectFile |
Path to the LabVIEW project (.lvproj). |
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 missing-in-project -ArgsJson '{
"LVVersion": "2020",
"SupportedBitness": "64",
"ProjectFile": "MyProject.lvproj"
}'
- name: Check for Missing Project Items
uses: LabVIEW-Community-CI-CD/open-source/missing-in-project@v1
with:
lv_version: '2020'
supported_bitness: '64'
project_file: 'MyProject.lvproj'
0
– no missing files detected1
– g-cli or VI error2
– missing files foundFor troubleshooting tips, see the troubleshooting guide.