Lunny Xiao eb792d9f8a Move database operations of merging a pull request to post receive hook and add a transaction (#30805) ... 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: wxiaoguang <wxiaoguang@gmail.com> (cherry picked from commit ebf0c969403d91ed80745ff5bd7dfbdb08174fc7) Conflicts: modules/private/hook.go routers/private/hook_post_receive.go trivial conflicts because 263a716cb5 * Performance optimization for git push (#30104) was not cherry-picked and because of 998a431747 Do not update PRs based on events that happened before they existed		2024-05-12 20:03:10 +02:00
..
tests/repos
actions.go
default_branch.go
hook_post_receive.go	Move database operations of merging a pull request to post receive hook and add a transaction (#30805)	2024-05-12 20:03:10 +02:00
hook_post_receive_test.go	Move database operations of merging a pull request to post receive hook and add a transaction (#30805)	2024-05-12 20:03:10 +02:00
hook_pre_receive.go
hook_proc_receive.go
hook_verification.go
hook_verification_test.go
internal.go
internal_repo.go
key.go
mail.go
main_test.go
manager.go
manager_process.go
manager_unix.go
manager_windows.go
restore_repo.go
serv.go
ssh_log.go