Skip to content

Webhook demilestoned contains milestone #32887

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
kim2048 opened this issue Dec 18, 2024 · 1 comment · Fixed by #32923
Closed

Webhook demilestoned contains milestone #32887

kim2048 opened this issue Dec 18, 2024 · 1 comment · Fixed by #32923
Labels

Comments

@kim2048
Copy link

kim2048 commented Dec 18, 2024

Description

Hello, when I receive the webhook action "demilestoned", the "issue.milestone" field is still set to the last milestone data. I'm not sure if this is a feature, but I thought the issue data I get in a webhook is always set to the current state (after the action happend) of the issue.

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Don't know, I'm only a small user ;)

Database

None

@kim2048
Copy link
Author

kim2048 commented Jan 6, 2025

Thank you :)

project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
Fix go-gitea#32887

(cherry picked from commit f44712f)

Conflicts:
	services/issue/milestone_test.go
  trivial conflicts (require vs assert)
(cherry picked from commit 2ffa9a5)
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Mar 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant