diff options
| author | zeripath <art27@cantab.net> | 2022-10-11 17:26:22 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-11 12:26:22 -0400 |
| commit | 4a2321210233e0b92c6e5894483e0929fb157a1b (patch) | |
| tree | dc7572aa6b906dd812cb33f7f404129b3e0e1518 /contrib/systemd/gitea.service | |
| parent | 5aceedc7fda39546a1e9fda423eb51a8286f86a7 (diff) | |
| download | gitea-4a2321210233e0b92c6e5894483e0929fb157a1b.tar.gz gitea-4a2321210233e0b92c6e5894483e0929fb157a1b.zip | |
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>
Diffstat (limited to 'contrib/systemd/gitea.service')
0 files changed, 0 insertions, 0 deletions