Typically PRs can take a little bit of time to review, Last month things were a bit slower due to holidays but I plan to get caught up on some of the backlog there over the next couple of weeks.
Typically when a change comes in that adds new functionality we need to test it and look to see if there are any documentation changes needed.
Looking at the Github actions quickly it looks like the build failed because of duplicate options in the trigger node so that would need to be resolved. I will update the GitHub repo when I have created the internal ticket for the review.
Nothing on your side really, It just comes down to time and resource. I spent last week looking through a lot of our older GitHub issues so I am almost there.
Hey @Jon,
there is the need to do some major changes to the node, before it can be reviewed.
I would be very pleased, if you can take a look at my latest question within the pull-request.