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
..
e2e	Playwright e2e test for taborder	2024-03-12 02:23:29 +01:00
fuzz	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
gitea-lfs-meta	Test views of LFS files (#22196)	2022-12-23 07:41:56 +08:00
gitea-repositories-meta	Allow non-admin users to delete review requests (#29057)	2024-02-26 22:30:27 +01:00
integration	Sync branches to DB immediately when handle git hook calling (gitea#29493)	2024-03-18 17:38:01 +01:00
testdata/data/attachments/a/0	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00
mssql.ini.tmpl	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
mysql.ini.tmpl	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
pgsql.ini.tmpl	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
sqlite.ini.tmpl	[TESTS] increase test-sqlite log level to Trace	2024-02-05 14:44:33 +01:00
test_utils.go	[TESTS] enable AddFixtures in unit tests	2024-03-03 11:11:26 +08:00