-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Webhook for "Issue Comment" contains no secret #4732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Confirmed issue still exists as of commit bd1bf2a. |
Would take a look at this tomorrow |
Similar to #5173 |
appleboy
pushed a commit
to go-gitea/go-sdk
that referenced
this issue
Oct 27, 2018
) affects webhooks for: * Delete * Fork * IssueComment * Release Resolves: go-gitea/gitea#4732, go-gitea/gitea#5173 Signed-off-by: Berengar W. Lehr <Berengar.Lehr@kompetenztest.de>
lafriks
pushed a commit
that referenced
this issue
Oct 30, 2018
…5208) * Updated dependency manager via `dep ensure -update code.gitea.io/sdk` * Gopkg.toml was not changed as sdk version is set to "master" * affects webhooks for: Delete, Fork, IssueComment, Release * also contains changes from go-gitea/go-sdk#125 and hence a swagger update Signed-off-by: Berengar W. Lehr <Berengar.Lehr@kompetenztest.de> Resolves: #4732, #5173
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
When setting up webhooks in gitea, I expect that every hook uses the secret one chooses.
But for
issue_comment
there is nosecret
field in the json which is send out.The send json:
To reproduce:
The text was updated successfully, but these errors were encountered: