Excluded sub directory not working

Hey there! The README.md provides an example where an excluded sub-path is provided. Unfortunately that sub-path still ends up in the cache. Here is a modified example using the local maven repository.

- name: Cache multiple paths
  uses: actions/cache@v2
  with:
    path: |
      ~/.m2
      !~/.m2/pro/taskana
    key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}

Reading out on the next (cached) build the files in ~/.m2/pro/taskana are contained in the cache. The following adjustment didn’t work either:

- name: Cache multiple paths
  uses: actions/cache@v2
  with:
    path: |
      ~/.m2
      !~/.m2/pro/taskana/**
    key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}

Is this a bug or am I having the wrong expectations? Our current workaround is to delete that subfolder in a dedicated step. It works, but is kinda annoying.

[bigdaz]

@dhadka Since it doesn’t appear that this issue will be resolved any time soon, I suggest that you update the example in the README. The current example is misleading since it won’t work as expected.

Changing ~/cache to ~/cache/* should be a functional example. ~/cache/* matches all subdirectories, and then !~/cache/exclude will exclude that particular subdirectory.

- name: Cache multiple paths
  uses: actions/cache@v2
  with:
    path: |
      ~/cache/*
      !~/cache/exclude
    key: ${{ runner.os }}-${{ hashFiles('**/lockfiles') }}

[dhadka]

@mustaphazorgati Thanks for reporting this (and sorry I didn’t see this earlier). I was able to reproduce this issue. I filed a bug over in the actions/toolkit repo that hosts the underlying logic for search patterns.