gitea/services
zeripath 4a23212102
Do DB update after merge in hammer context (#21401)
When merge was changed to run in the background context, the db updates
were still running in request context. This means that the merge could
be successful but the db not be updated.

This PR changes both these to run in the hammer context, this is not
complete rollback protection but it's much better.

Fix #21332

Signed-off-by: Andrew Thornton <art27@cantab.net>

Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2022-10-11 12:26:22 -04:00
..
agit
asymkey
attachment
auth SessionUser protection against nil pointer dereference (#21358) 2022-10-06 21:50:38 +01:00
automerge
comments
context
cron
externalaccount
forms
gitdiff Stop logging CheckPath returns error: context canceled (#21064) 2022-10-10 21:54:30 +01:00
issue
lfs
mailer
migrations Foreign ID conflicts if ID is 0 for each item (#21271) 2022-10-02 17:43:16 -04:00
mirror
org
packages
pull Do DB update after merge in hammer context (#21401) 2022-10-11 12:26:22 -04:00
release
repository Refactor parseTreeEntries, speed up tree list (#21368) 2022-10-08 01:20:53 +08:00
task
user
webhook Fix formatted link for PR review notifications to matrix (#21319) 2022-10-07 22:06:34 +01:00
wiki