-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Fix issue comment number #30556
Fix issue comment number #30556
Conversation
How much work would it be to add a migration that fixes the counts on existing issues? Would probably be a long-running migration on big instances, right? Also, not sure if such a migration would be backportable at all as it would likely skip migration numbers (a design flaw in the migration system). |
Yes, so I don't think the migration is necessary. The number will be corrected when next comment created/updated.
|
Yeah it's not really a requirement from me, more like a "nice to have" but likely too complicated with the migration backport to really be justified. |
Willing to approve this without migration once you fix the tests :) |
ee21b92
to
9c4d250
Compare
CI failure is related |
* giteaofficial/main: Fix issue comment number (go-gitea#30556) Fix duplicate co-author in squashed merge commit messages (go-gitea#33020) Merge updatecommentattachment functions (go-gitea#33044) Move SetMerged to service layer (go-gitea#33045) Remove aws go sdk package dependency (go-gitea#33029) Fix settings not being loaded at CLI (go-gitea#26402) Refactor fixture loading for testing (go-gitea#33024) Use gitrepo.GetTreePathLatestCommit to get file lastest commit instead from latest commit cache (go-gitea#32987) Fix bug automerge cannot be chosed when there is only 1 merge style (go-gitea#33040) use `-s -w` ldflags for release artifacts (go-gitea#33041)
Fix #22419
Only comments with types
CommentTypeComment
andCommentTypeReview
will be counted as conversations of the pull request.CommentTypeReview
was missed in the previous implementation.