From 43514fecdd43d91ba89bbda57e8a9a12a8753395 Mon Sep 17 00:00:00 2001
From: Daniel McNab <36049421+DJMcNab@users.noreply.github.com>
Date: Fri, 26 Jul 2024 12:28:05 +0100
Subject: [PATCH] Abort the LFS experiment in CI (#646)

Apparently this is more likely to get a speedy approval
---
 .github/workflows/ci.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 72abb06c3..f40cd6f4c 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -147,9 +147,9 @@ jobs:
         restore-keys: vello-lfs-
         enableCrossOsArchive: true
 
-    - name: Fetch lfs data
-      if: ${{ steps.lfs-cache.outputs.cache-hit != 'true' }}
-      run: git lfs fetch
+    # - name: Fetch lfs data
+    #   if: ${{ steps.lfs-cache.outputs.cache-hit != 'true' }}
+    #   run: git lfs fetch
   
   test-stable:
     name: cargo test
@@ -219,7 +219,7 @@ jobs:
           # We are experimenting with git lfs, and we don't expect to run out of bandwidth.
           # However, if we do, the tests are designed to be robust against that, if this environment variable is set.
           # If we do run out of bandwidth, uncomment the following line and inform @DJMcNab.
-          # VELLO_SKIP_LFS_SNAPSHOTS: all
+          VELLO_SKIP_LFS_SNAPSHOTS: all
 
   test-stable-wasm:
     name: cargo test (wasm32)