bramd/Prepare NVDA source
Checkout and build a runnable NVDA source tree for add-on development (scons source)
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 10, 2026
- License
- GPL 2.0
Pinned Snippet
uses: bramd/prepare-nvda-source@52bae21bef39e9eff77ef7a84c378ad159c4ad07 # v1.1.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| python-version | Python version to install. Leave empty to auto-detect it from NVDA's .python-versions file (requires NVDA >= 2025.3). An explicit value overrides the auto-detected one. | no | "" |
| python-arch | Python architecture (x86 or x64). Leave empty to auto-detect it from NVDA's .python-versions file (requires NVDA >= 2025.3). An explicit value overrides the auto-detected one. | no | "" |
| nvda-ref | Git ref to checkout (tag or branch) | yes | — |
| github-token | GitHub token for API access (used to resolve the NVDA ref to a commit SHA) | yes | — |
| scons-args | Extra arguments appended to `scons source` (e.g. -j2, version=...) | no | -j2 |
| install-vs-components | Whether to install the VS components from NVDA's .vsconfig at runtime. Set to false on runner images that already ship the required Visual Studio toolset (e.g. the standard windows-2025-vs2026 image) to skip the install and behave like nvaccess/nvda's own build. | no | true |
| vs-version | Major Visual Studio version to select when installing components (e.g. 17 for VS 2022, 18 for VS 2026). Leave empty to use the latest installed VS. Only used when install-vs-components is true. | no | "" |
Outputs
| name | description |
|---|---|
| nvda-path | Path to the built NVDA source tree, relative to the workspace |
| cache-hit | Whether the NVDA cache was hit |