This action is useful if you want to integrate NVGT scripting language into your GitHub action (GA) workflow.
The action supports the following operating systems:
windows-latest: Windowsubuntu-latest: Linuxmacos-latest: Mac OS
name: Build NVGT
on: push
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- name: Setup NVGT
# ID is required if you want to retrieve outputs.
id: nvgt
uses: harrymkt/setup-nvgt@v1.0.8
with:
latest: true
- name: Build
# Your own build here. i.e.
run: nvgt -c your_script.nvgtProvide variables with the ${{ steps.*.with }} parameter:
latest(boolean) optional: Should the action fetch the latest release as possible? Defaults totrue.version(string) optional: The NVGT version you want to install if not latest. Eg,0.89.1_beta. Defaults to none. This input will be ignored if eitherlatestordevistrue.dev(boolean) optional: Toggles whether it should download latest development version.add_to_path(boolean) optional: NVGT installed directory should be added to path directory. Defaults totrue.tools(string) optional: A list of tools to install, see below. This can install multiple tools by separating them with lines. Each tool can optionally add a tag, i.e.tool_name@tag_name, where tag name is one of the following:latest: Represents the latest possible release. This is equivalent to justtool_namewithout a tag.dev: Represents the bleeding edge development version.- Otherwise, the name after the
@character is considered a version, for example, 1.0.0, v1.0.0 etc.
Use the ${{ steps.<id>.outputs.<var_name> }} to retrieve the output. The following output variables are available:
path(string): Path to the NVGT installed directory.
The following is a list of tools available to install using tools input:
| Name | Description |
|---|---|
nvgtpm |
The NVGT package manager, currently unofficial |