proposal: keep_ files can be a string type, filtering files through wildcards.

[tidys]

Checklist

• [X] I am using the latest version of this action.
• [X] I have read the latest README and followed the instructions.
• [X] I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal

I feel like keeping Files can be a string type, like excude Like assets, filtering files through wildcards.

Describe the solution you'd like

Simply put, my requirement is not to delete certain files in Warehouse B during synchronization, such as github action, readme.md, and so on.

Describe alternatives you've considered

Currently, I have executed two actions

• The first time was

  Keep_ Files: true
  Exclude_ Assets: '*. js, *. css'

  By excluding_ Assets delete all hash files

• Second time

  Keep_ Files: true
  Exclude_ Assets: ''

  Keep the previous state and synchronize the hash file again, but no files will be deleted this time

This can achieve my goal twice, but it doesn't feel very good

Additional context

I want to synchronize a directory from warehouse A to warehouse B,

But I have my own github action in Warehouse B, and I don't want the github action file in Warehouse B to be deleted

So I used keep_ Files option.

But the file I synchronized to Warehouse B is a website, and the JS and CSS file names have hashes,

For example, index.hash.js,

If I use keep_ Files

This will cause a lot of index. hash.js files to appear in the files synchronized with Warehouse B,

Actually, all you need is an index. has.js.

Later on, I discovered that exclude_ Assets, after reading the relevant code, I found that deleting the relevant files after synchronizing them to warehouse B does not meet my needs.