Generating a Task Matrix by Looping over Repo Files with GitHub Actions

I’ve been having more fun with GitHub actions after Automating Code Changes via GitHub Actions Making Pull Requests. Let’s generate a job matrix from a list of files. Why would I need that? In opensearch-project/opensearch-build we create manifest files that are used to produce an OpenSearch distribution. These files are created manually, one for every version. Each needs to be sanity-checked when created or changed. These checks can be executed in parallel, so we can create a GitHub Actions mat...

Submit