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
..
api	Remove deprecated stuff for runners (#30930)	2024-05-12 20:03:10 +02:00
common	feat(api): implement branch/commit comparison API (#30349)	2024-04-21 11:58:18 +02:00
install	s/Gitea/Forgejo in various log messages and comments	2024-04-21 21:26:15 +05:00
private	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
utils	[PORT] drop utils.IsExternalURL (and expand IsRiskyRedirectURL tests) (#3167)	2024-04-15 13:03:08 +00:00
web	Move reverproxyauth before session so the header will not be ignored even if user has login (#27821)	2024-05-12 20:03:10 +02:00
init.go	s/Gitea/Forgejo in various log messages and comments	2024-04-21 21:26:15 +05:00