Giteabot ec3f5f9992 Move database operations of merging a pull request to post receive hook and add a transaction (#30805) (#30888) ... Backport #30805 by @lunny Merging PR may fail because of various problems. The pull request may have a dirty state because there is no transaction when merging a pull request. ref https://github.com/go-gitea/gitea/pull/25741#issuecomment-2074126393 This PR moves all database update operations to post-receive handler for merging a pull request and having a database transaction. That means if database operations fail, then the git merging will fail, the git client will get a fail result. There are already many tests for pull request merging, so we don't need to add a new one. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>		2024-05-08 14:17:18 +00:00
..
actions.go	Return responseText instead of string in some functions (#28836)	2024-01-19 10:45:23 +08:00
hook.go	Move database operations of merging a pull request to post receive hook and add a transaction (#30805) (#30888)	2024-05-08 14:17:18 +00:00
internal.go	Refactor internal API for git commands, use meaningful messages instead of "Internal Server Error" (#23687)	2023-03-29 14:32:26 +08:00
key.go	Return responseText instead of string in some functions (#28836)	2024-01-19 10:45:23 +08:00
mail.go	Return responseText instead of string in some functions (#28836)	2024-01-19 10:45:23 +08:00
manager.go	Replace interface{} with any (#25686)	2023-07-04 18:36:08 +00:00
request.go	Return responseText instead of string in some functions (#28836)	2024-01-19 10:45:23 +08:00
restore_repo.go	Fix regression: access log template, gitea manager cli command (#24838)	2023-05-22 09:38:38 +08:00
serv.go	Refactor internal API for git commands, use meaningful messages instead of "Internal Server Error" (#23687)	2023-03-29 14:32:26 +08:00