Gusted 331fa44956 [BUG] Ensure HasIssueContentHistory takes into account comment_id ... - The content history table contains the content history of issues and comments. For issues they are saved with an comment id of zero. - If you want to check if the issue has an content history, it should take into account that SQL has `comment_id = 0`, as it otherwise could return incorrect results when for example the issue already has an comment that has an content history. - Fix the code of `HasIssueContentHistory` to take this into account, it relied on XORM to generate the SQL from the non-default values of the struct, this wouldn't generate the `comment_id = 0` SQL as `0` is the default value of an integer. - Remove an unncessary log (it's not the responsibility of `models` code to do logging). - Adds unit test. - Resolves #2513		2024-02-29 18:23:06 +01:00
..
actions
activities
admin
asymkey
auth
avatars
db
dbfs
fixtures
forgejo/semver
forgejo_migrations
git
issues
migrations
organization
packages
perm
project
pull
repo
secret
shared/types
system
unit	Add a direct link from repo header to unit settings	2024-02-13 22:42:09 +01:00
unittest
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go