git-for-windows/Setup Git for Windows SDK

Set up an environment to develop Git for Windows

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jul 10, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: git-for-windows/setup-git-for-windows-sdk@335917db02da4280d3d5e87915d7b86196677f9f # v2.1.0

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
flavor	The subset (if any) of the SDK: minimal, makepkg-git, build-installers, or full	no	minimal
architecture	The architecture of the SDK: x86_64, i686, aarch64, or ucrt64. Note that "aarch64" only supports the "full" flavor for now. "ucrt64" selects the UCRT64 variant of git-sdk-64; while the MINGW64-to-UCRT64 migration is in progress it is cloned from a transitional "ucrt64" branch that will eventually replace "main", at which point "x86_64" itself will materialise a UCRT64 SDK.	no	x86_64
msys	Whether to start in MSYS mode (defaults to false)	no	false
path	Where to write the SDK files	no	""
cleanup	Whether to clean up SDK files. This is only needed on self-hosted runners that are reused for multiple jobs.	no	false
verbose	Whether to log files as they are extracted	no	250
cache	Use @actions/cache to accelerate this Action. Note: GitHub Actions caches are shared across branches and workflows within a repository, which makes them susceptible to cache-poisoning attacks (see e.g. Cacheract, https://github.com/AdnaneKhan/Cacheract). Caching is therefore disabled by default.	no	false
github-token	Personal access token (PAT) used to call into GitHub's REST API. We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)	—	${{ github.token }}

Outputs

no outputs