Erik Burton

Closes #1260.

This action is likely to break on May 13 - see https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/. > Node16 has been out of support since [September 2023](https://github.com/nodejs/Release/#end-of-life-releases). As a result we have started the deprecation...

Although Github extended the deprecation of node16 by a few months, I have removed any of my dependencies on this action. I unfortunately suggest you do the same.

Relevant blog post: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

We have a process that happens in two steps: ### Step 1 A PR is created and it : 1. Adds some amount json files to a specific directory located...

Another solution which doesn't overload `changed_files` predicate would be to add a couple more predicates like `added_files` `modified_files` `deleted_files`, also implementing similar functionality to `changed_paths` but limiting them to specific...

Thank you! I will try this out and get back to you 😄

I appreciate the help with the rules you've setup, they accomplish the goals, thank you for taking the time with that! As you've called out - it's non-obvious, and we'd...

Thank you for the review! Sorry for the delay, was caught up with some deadlines. I've changed the phrases around using some of your suggestions. To get around the weird...

This is also happening to us, but in a slightly different scenario. We had [this workflow](https://github.com/smartcontractkit/chainlink/actions/runs/12774483140/job/35608692272?pr=15874#step:10:3) seemingly create the cache, although with warnings. ``` Post job cleanup. /usr/bin/tar --posix -cf...