-
Notifications
You must be signed in to change notification settings - Fork 409
Description
I am proposing to the Apache Spark community that we use this Action to manage the number of open PRs we have.
Enabling this Action on a large repo with so many contributors is not a single-step task. Project committers will want to see how the Action works and iterate several times on the wording of things and, more importantly, on the filter that selects which PRs to close or not.
My desired workflow is to submit a PR to the Spark repo adding this Action in. From the PR, I want to be able to iterate on the filter criteria and see what PRs would be impacted, without actually impacting anything.
Is there way to do a dry run of this Action, where we can see the list of PRs that would be impacted, along with the details of how each one would be impacted, without actually touching any PRs?