This action primary aim is to create a Windows Dev Drive on your behalf and expose its location via GitHub Environment Variables.

Dev Drives use ReFS under the hood to provide optimizations that are targeted for Developer workflows. By using a Dev Drive, you can increase performance significantly on a variety of developer workloads. See related blog post.

You can still decide to use something else than ReFS and get speed benefits of a Virtual Hard Disk (VHDX) that this action creates for you.

Just add the following line to the steps: list in your GitHub Actions yaml:

- uses: samypr100/setup-dev-drive@v2

You can optionally pass parameters to the action as follows:

- uses: samypr100/setup-dev-drive@v2
  with:
    drive-size: 1GB
    drive-format: ReFS
    drive-type: Fixed
    drive-path: "dev_drive.vhdx"
    mount-if-exists: false
    workspace-copy: true

Allows you to configure the Dev Drive size. This is subject to the limit of space available on your runner. The default public runners roughly hold about 15GB of space, so it's suggested you keep your drive size below that limit, or you may encounter errors.

The format of the drive, by default ReFS but it can be any of FAT, FAT32, exFAT, NTFS, ReFS as provided by Format-Volume.

The path to the Dev Drive VHDX file, by default resolves to C:\dev_drive.vhdx. Note, when a relative path is provided, it will be relative to C:\ or the default workspace drive letter.

When an absolute path is provided, make sure it's located outside ${{ github.workspace }} otherwise workspace-copy can cause issues.

Determines the type of drive, Fixed or Dynamic. There are performance tradeoffs between both. For the purposes of this action Dynamic is used by default for flexibility.

Dynamic is useful when you want to cache the disk across job runs as it yields a smaller payload to cache when the job ends.

Fixed gives you a notable performance boost, but there's a small creation overhead.

Mounts the Dev Drive if it already exists at drive-path location. When it does not exist, it will fall back to creating one at that location instead. This is useful when your workflow caches the Dev Drive for further use in other jobs via actions/cache.

This copies ${{ github.workspace }} to your Dev Drive. Usually when you use actions/checkout it creates a shallow copy of your commit to ${{ github.workspace }}. When workspace-copy is set to true it will copy your workspace into your dev drive allowing you move your workload to be purely on the dev drive.

This option was needed since actions/checkout does not allow cloning outside ${{ github.workspace }}. See actions/checkout#197.

These environment variables are meant to be used along working-directory to make sure your workflow commands are executing relative to your Dev Drive.

Contains the path to your dev drive of the form <DRIVE_LETTER>:. For example if the dev drive assigned letter is E, ${{ env.DEV_DRIVE }} will contain E:.

When workspace-copy is set to true, this contains the workspace location as represented by the dev drive location. For example if your GitHub workspace is C:\a\<project-name>\<project-name> your dev drive workspace will be E:\<project-name> by default assuming the drive letter is E.

The canonical location of the VHDX file.

When drive-path is set to a relative path like my_drive.vhdx the location in this variable will likely be C:\my_drive.vhdx.

On the other hand, when drive-path is set to an absolute path, that's likely what this variable will contain after normalization.

- uses: actions/checkout@v4
- uses: samypr100/setup-dev-drive@v2
  with:
    workspace-copy: true
- name: Install Dependencies
  working-directory: ${{ env.DEV_DRIVE_WORKSPACE }}
  run: npm install

- uses: samypr100/setup-dev-drive@v2
- name: "Install Rust toolchain in dev drive"
  env:
    CARGO_HOME: ${{ env.DEV_DRIVE }}/.cargo
    RUSTUP_HOME: ${{ env.DEV_DRIVE }}/.rustup
  run: rustup show

This action currently only works on Windows runners. In particular, this action will only work with windows-2022 or windows-latest runners.

For Native Dev Drive support, 10.0.22621 build or later of windows is required. This action will gracefully still work even if Native Dev Drive is not available.

On cases where runners may still not be updated to meet the minimum version, you can still get speed gains by using this action due to ReFS and VHDX usage.

Thanks to Paco Sevilla for the idea to use a VHDX within a Github Workflow.