-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Webhook sent twice on the newest version #676
Comments
@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 P.s: It does look like you have set up a second step. What is the difference between |
Hi, @joelwmale just to mention I'm running on self-hosted runners on aws , just play with the tag of the version from master to 2.3.2 and put a working webhook url this is the workflow I used to test:
|
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. |
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!
The text was updated successfully, but these errors were encountered: