We're using this action with a slightly unusual model, with one workflow dispatching to several other workflows to get them to run in parallel with easy result tracking. The action currently fails, with the error shown below. This is within a private repo, so security implications are different than a public repo. It would be great to still be able to use this action, gated by a config option.

Error: This action has only been designed to work for "pull_request", "push", "workflow_run", "schedule" or "merge_group" actions, not "workflow_dispatch". Because there are security implications. If you have a different usecase, please open an issue, we'll be glad to add compatibility.

Desired result

Add a config flag to allow this. The challenge is event to activity mapping -- if it's not a PR, it's harder to tell if this was a merge or not. This could mean the flag is a map, or two flags -- one a list of events to save data files on, the other a list of events to treat as PRs?

I'm happy to implement, but wanted feedback on the design.