mirror of
https://github.com/joelwmale/webhook-action.git
synced 2026-06-12 10:45:58 -05:00
Webhook sent twice on the newest version #18
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @omer2500 on GitHub (Mar 31, 2024).
Hi,
We have a job that sends a webhook on a workflow
A couple of hours ago it started to send the webhook twice each time it ran.
we are using the tag master and I saw that a new version was released 3 days ago
what I see is that we have another step called Post webhook that sends the webhook again and have the same logs
on 2.3.2 it doesn't happen
I'm attaching pictures to show the issue
latest version:

2.3.2:
is this intentional? am I missing some new configuration ? or is this a bug?
Thanks!
@joelwmale commented on GitHub (Mar 31, 2024):
@omer2500 Can you send me the workflow file and how you've set up this step?
Testing this on the master version (prior to release, using
develop) never sent the webhook twice.P.s: It does look like you have set up a second step. What is the difference between
webhookandpost webhooksteps?@omer2500 commented on GitHub (Mar 31, 2024):
Hi, @joelwmale
I have no step called Post webhook,
the log is the same except It mentions its a cleanup job but right after that log I see the log that indicated webhook sent
just to mention I'm running on self-hosted runners on aws ,
so you might need to adjust the runs-on property
just play with the tag of the version from master to 2.3.2 and put a working webhook url
and check the steps that were executed
this is the workflow I used to test:
@joelwmale commented on GitHub (Mar 31, 2024):
Hey @omer2500 apologies, seems like it was an oversight on my behalf in the action configuration file. Try again using the latest master (v2.4.1). Should be fixed now.