Skip to content

Conversation

drsybren
Copy link
Contributor

This is a fix for #22510

The code assumed that the AssigneeID from the comment YAML was an int64, but it is actually an int, causing a panic. It also had no check on whether the type cast was actually valid, so badly formatted YAML could also cause a panic.

Both these issues have been fixed.

This is a fix for go-gitea#22510

The code assumed that the `AssigneeID` from the comment YAML was an
`int64`, but it is actually an `int`, causing a panic. It also had no
check on whether the type cast was actually valid, so badly formatted
YAML could also cause a panic.

Both these issues have been fixed.
@jolheiser jolheiser added type/bug skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. labels Jan 19, 2023
@jolheiser jolheiser added this to the 1.19.0 milestone Jan 19, 2023
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jan 19, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jan 19, 2023
@techknowlogick techknowlogick merged commit b383652 into go-gitea:main Jan 19, 2023
@drsybren drsybren deleted the blender-fix-assignee-comment branch January 24, 2023 16:09
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants