-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Labels
Comments
lunny
added a commit
that referenced
this issue
Dec 25, 2024
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Dec 25, 2024
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)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: