Cameron Moore

I didn't catch that in your original post, but the "not" value is an array of objects. Try this: ```json "trigger-rule": { "not": [ { "match": { "type": "value", "value":...

@volcano1111, I doubt I'll have time to work it in the immediate future. It's not a trivial issue to resolve. I'll add it to the v2.9.0 milestone and hope that...

@foosinn, If you're asking about rate-limiting hook executions, this is a duplicate of #120. It was closed because @adnanh didn't have time to implement it back then even though @antoineco...

Sorry, I wasn't sure exactly what you meant. "Time based" sounds like rate limiting so assumed that's what you meant. Can you please flesh out your request? Can you offer...

That feature was added in 2.7.0.

Perhaps @adnanh has some insight. I deploy webhook with a private Ansible role and avoid rpm/deb/snap packages.

Interesting request. My thoughts on how this could work: The `pass-arguments-to-command` property [shares the same type](https://github.com/adnanh/webhook/blob/38294cd0c6dd2f3535e91188ce8d69536b72eb1a/internal/hook/hook.go#L512-L515) ([`[]Argument`](https://github.com/adnanh/webhook/blob/38294cd0c6dd2f3535e91188ce8d69536b72eb1a/internal/hook/hook.go#L397)) as the `pass-environment-to-command`, `pass-file-to-command`, and `parse-parameters-as-json` options. The simplest solution would be to...

You have a permissions problem. The process running webhook must be able to access the exec path and execute it. See also: #516

> The problem is the poor error handling and poor error logging \[...\] over the typo in the hooks.yaml How would anyone know that based upon your initial report? So,...

@Drugoy, I get that you're frustrated, but I'd still like to see a detailed report of the problem. What exactly was the typo? What was the fix? What error message...