You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
when I create an issue via web ui with a label and an assignee I get 3 webhook calls in this order: assigned, opened, label_updated. I don't know if I could expect a specific order here, but it's fine.
The assigned issue json already contains all the issue data (user, assignee, my label, state, ...) except the created_at and updated_at fields: They contain a 0 epoch ("1970-01-01T01:00:00+01:00") and have only correct values in the opened and label_updated json (all other fields are the same in all 3 calls).
My assumption was, that I would never get an "uninitialized" created_at field in any webhook issue value. Am I right?
Gitea Version
1.23.7
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?
I don't know
Database
None
The text was updated successfully, but these errors were encountered:
Description
Hello,
when I create an issue via web ui with a label and an assignee I get 3 webhook calls in this order:
assigned
,opened
,label_updated
. I don't know if I could expect a specific order here, but it's fine.The
assigned
issue json already contains all the issue data (user, assignee, my label, state, ...) except thecreated_at
andupdated_at
fields: They contain a 0 epoch ("1970-01-01T01:00:00+01:00"
) and have only correct values in theopened
andlabel_updated
json (all other fields are the same in all 3 calls).My assumption was, that I would never get an "uninitialized"
created_at
field in any webhook issue value. Am I right?Gitea Version
1.23.7
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?
I don't know
Database
None
The text was updated successfully, but these errors were encountered: