Stop caching on CI

The only thing we now cache is cargo-cache, which we only use for cache.
That's a catch-22 if I ever seen one. And for Clippy itself we always
want to do a clean build and not cache anything.

.github/workflows/clippy.yml

@@ -41,14 +41,6 @@ jobs:
     - name: Install toolchain
       run: rustup show active-toolchain
 
-    - name: Cache cargo dir
-      uses: actions/cache@v2
-      with:
-        path: ~/.cargo
-        key: ${{ runner.os }}-x86_64-unknown-linux-gnu-v2-${{ hashFiles('Cargo.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-x86_64-unknown-linux-gnu
-
     # Run
     - name: Set LD_LIBRARY_PATH (Linux)
       run: |
@@ -88,9 +80,3 @@ jobs:
         cargo dev new_lint --name new_late_pass --pass late
         cargo check
         git reset --hard HEAD
-
-    # Cleanup
-    - name: Run cargo-cache --autoclean
-      run: |
-        cargo install cargo-cache --no-default-features --features ci-autoclean cargo-cache
-        cargo cache

.github/workflows/clippy_bors.yml

@@ -91,14 +91,6 @@ jobs:
     - name: Install toolchain
       run: rustup show active-toolchain
 
-    - name: Cache cargo dir
-      uses: actions/cache@v2
-      with:
-        path: ~/.cargo
-        key: ${{ runner.os }}-${{ matrix.host }}-v2-${{ hashFiles('Cargo.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-${{ matrix.host }}
-
     # Run
     - name: Set LD_LIBRARY_PATH (Linux)
       if: runner.os == 'Linux'
@@ -144,12 +136,6 @@ jobs:
       env:
         OS: ${{ runner.os }}
 
-    # Cleanup
-    - name: Run cargo-cache --autoclean
-      run: |
-        cargo install cargo-cache --no-default-features --features ci-autoclean cargo-cache
-        cargo cache
-
   integration_build:
     needs: changelog
     runs-on: ubuntu-latest
@@ -166,14 +152,6 @@ jobs:
     - name: Install toolchain
       run: rustup show active-toolchain
 
-    - name: Cache cargo dir
-      uses: actions/cache@v2
-      with:
-        path: ~/.cargo
-        key: ${{ runner.os }}-x86_64-unknown-linux-gnu-v2-${{ hashFiles('Cargo.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-x86_64-unknown-linux-gnu
-
     # Run
     - name: Build Integration Test
       run: cargo test --test integration --features integration --no-run
@@ -193,11 +171,6 @@ jobs:
         name: target
         path: target
 
-    # Cleanup
-    - name: Run cargo-cache --autoclean
-      run: |
-        cargo install cargo-cache --no-default-features --features ci-autoclean cargo-cache
-        cargo cache
   integration:
     needs: integration_build
     strategy:
@@ -237,14 +210,6 @@ jobs:
     - name: Install toolchain
       run: rustup show active-toolchain
 
-    - name: Cache cargo dir
-      uses: actions/cache@v2
-      with:
-        path: ~/.cargo
-        key: ${{ runner.os }}-x86_64-unknown-linux-gnu-v2-${{ hashFiles('Cargo.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-x86_64-unknown-linux-gnu
-
     # Download
     - name: Download target dir
       uses: actions/download-artifact@v1
@@ -262,12 +227,6 @@ jobs:
         INTEGRATION: ${{ matrix.integration }}
         RUSTUP_TOOLCHAIN: master
 
-    # Cleanup
-    - name: Run cargo-cache --autoclean
-      run: |
-        cargo install cargo-cache --no-default-features --features ci-autoclean cargo-cache
-        cargo cache
-
   # These jobs doesn't actually test anything, but they're only used to tell
   # bors the build completed, as there is no practical way to detect when a
   # workflow is successful listening to webhooks only.