forgejo/models
Jason Song 286d09203f Sync branches to DB immediately when handle git hook calling (gitea#29493)
Unlike other async processing in the queue, we should sync branches to
the DB immediately when handling git hook calling. If it fails, users
can see the error message in the output of the git command.

It can avoid potential inconsistency issues, and help #29494.

---------

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2024-03-18 17:38:01 +01:00
..
actions Make runs-on support variable expression (#29468) 2024-03-11 23:36:59 +07:00
activities
admin
asymkey
auth
avatars
db Partially enable MSSQL case-sensitive collation support (#29238) 2024-03-11 23:36:59 +07:00
dbfs
fixtures Store webhook event in database (#29145) 2024-03-11 23:36:59 +07:00
forgejo/semver
forgejo_migrations
git Sync branches to DB immediately when handle git hook calling (gitea#29493) 2024-03-18 17:38:01 +01:00
issues [BUG] Use correct headcommitid 2024-03-14 16:15:56 +01:00
migrations add test for webhook migration 2024-03-11 23:37:00 +07:00
organization
packages
perm
project Partially enable MSSQL case-sensitive collation support (#29238) 2024-03-11 23:36:59 +07:00
pull
repo
secret Make runs-on support variable expression (#29468) 2024-03-11 23:36:59 +07:00
shared/types
system
unit
unittest [Windows] prevent ? in testdata path 2024-03-15 13:15:46 +01:00
user
webhook Store webhook event in database (#29145) 2024-03-11 23:36:59 +07:00
error.go
fixture_generation.go
fixture_test.go
main_test.go
org.go
org_team.go
org_team_test.go
org_test.go
repo.go
repo_test.go
repo_transfer.go
repo_transfer_test.go