When a GitHub branch is deleted, GitHub sends both a delete event and a push event with "deleted": true in the payload. Currently, Harness activates a push-based trigger for the push payload which is coming from a branch deletion event that is resulting in an unintended pipeline execution.

Can we check the possibilities of enhancing the GitHub trigger handling to recognize branch-deletion push events and prevent the push trigger activation, without requiring users to add custom payload conditions such as <+trigger.payload.deleted> != true.

The existing dedicated Delete event configuration should be sufficient to control branch-deletion-triggered executions.