Skip to content

issue_label and issue_milestone webhooks not triggered on new issue #14352

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

Closed
1 task done
jpraet opened this issue Jan 15, 2021 · 2 comments · Fixed by #14363
Closed
1 task done

issue_label and issue_milestone webhooks not triggered on new issue #14352

jpraet opened this issue Jan 15, 2021 · 2 comments · Fixed by #14363
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@jpraet
Copy link
Member

jpraet commented Jan 15, 2021

Description

The issue_label, issue_milestone, pull_request_label and pull_request_milestone webhooks are not triggered when you immediately provide the label or milestone when creating the new issue/pr. When adding the label or milestone AFTER the issue/pr has already been created it works fine.

This is not consistent with the issue_assign/pull_request_assign webhooks: these also get triggered if you provide the assignee immediately when creating the new issue/pr.

Screenshots

image

The webhook:

image

Only receives the notification for the issue_assign.

image

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jan 16, 2021
@lunny
Copy link
Member

lunny commented Jan 16, 2021

Should we remove all extra events when create an issue/pull request or add them all?

@jpraet
Copy link
Member Author

jpraet commented Jan 16, 2021

Emitting the labeled/milestoned/assigned events regardless of whether they were added at creation time or afterwards seems most intuitive to me, from the point of view of configuring and implementing a webhook.

@lafriks lafriks added this to the 1.14.0 milestone Jan 17, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Mar 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants