3 people 680f2a2598 fix: don't roll back branches on out-of-order post-receive hooks (#40110) ...

The post-receive hook wrote each push's new commit into the branch
table. Each push runs its own hook after the ref is updated, so with
pushes in close succession, like CI pushing back or a quick force-push,
a slower first hook can finish last. The table then keeps the older
commit, or marks a re-created branch as deleted.

- The sync reads each pushed branch's state from git under a repo-scoped
lock
- Deletions go through the same sync, so a re-created branch stays
active
- A branch that fails to sync is logged and skipped instead of aborting
the batch

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: Giteabot <teabot@gitea.io>

2026-10-31 17:31:47 +01:00

..

api

fix: list bot users in gitea admin user list and admin users API (#40060)

2026-10-31 12:30:07 +00:00

common

fix: correctly parse and validate forwarded client IPs and remove unmaintained chi-middleware/proxy (#39190)

2026-10-23 09:25:04 +00:00

install

refactor: "install" page (#39400)

2026-09-23 23:14:31 +00:00

private

fix: don't roll back branches on out-of-order post-receive hooks (#40110)

2026-10-31 17:31:47 +01:00

utils

Refactor flash message and remove SanitizeHTML template func (#37179)

2026-04-12 10:17:25 +08:00

web

fix(projects): hide linked pull requests the viewer cannot read (#40016)

2026-10-31 17:31:34 +01:00

init.go

refactor!: remove go-git backend (#39487)

2026-10-03 10:04:24 +00:00