forgejo/models
Lunny Xiao 14750f3d11
Also sync DB branches on push if necessary (#28361) (#28403)
Fix #28056
Backport #28361

This PR will check whether the repo has zero branch when pushing a
branch. If that, it means this repository hasn't been synced.

The reason caused that is after user upgrade from v1.20 -> v1.21, he
just push branches without visit the repository user interface. Because
all repositories routers will check whether a branches sync is necessary
but push has not such check.

For every repository, it has two states, synced or not synced. If there
is zero branch for a repository, then it will be assumed as non-sync
state. Otherwise, it's synced state. So if we think it's synced, we just
need to update branch/insert new branch. Otherwise do a full sync. So
that, for every push, there will be almost no extra load added. It's
high performance than yours.

For the implementation, we in fact will try to update the branch first,
if updated success with affect records > 0, then all are done. Because
that means the branch has been in the database. If no record is
affected, that means the branch does not exist in database. So there are
two possibilities. One is this is a new branch, then we just need to
insert the record. Another is the branches haven't been synced, then we
need to sync all the branches into database.

(cherry picked from commit 87db4a47c8)
2023-12-12 15:21:33 +01:00
..
actions Fix no ActionTaskOutput table waring (#28149) (#28152) 2023-11-22 17:12:12 +01:00
activities [MODERATION] User blocking 2023-11-13 13:58:02 +01:00
admin
asymkey Fix comment permissions (#28213) (#28216) 2023-11-26 13:56:50 +01:00
auth [GITEA] rework long-term authentication 2023-11-13 14:06:31 +01:00
avatars Refactor system setting (#27000) (#27452) 2023-10-05 10:37:59 +00:00
db Also sync DB branches on push if necessary (#28361) (#28403) 2023-12-12 15:21:33 +01:00
dbfs
fixtures Fix comment permissions (#28213) (#28216) 2023-11-26 13:56:50 +01:00
forgejo/semver [UPGRADE] add sanity checks for [storage*] 2023-11-13 12:33:49 +01:00
forgejo_migrations [GITEA] rework long-term authentication 2023-11-13 14:06:31 +01:00
git Also sync DB branches on push if necessary (#28361) (#28403) 2023-12-12 15:21:33 +01:00
issues Fix comment permissions (#28213) (#28216) 2023-11-26 13:56:50 +01:00
migrations handle repository.size column being NULL in migration v263 (#28336) (#28363) 2023-12-08 13:41:16 +01:00
organization
packages
perm
project Fix comment permissions (#28213) (#28216) 2023-11-26 13:56:50 +01:00
pull [GITEA] GetScheduledMergeByPullID may involve a system user 2023-12-11 18:43:03 +01:00
repo Also sync DB branches on push if necessary (#28361) (#28403) 2023-12-12 15:21:33 +01:00
secret
shared/types
system Increase "version" when update the setting value to a same value as before (#28243) (#28244) 2023-12-08 13:40:59 +01:00
unit
unittest [GITEA] Introduce HTTP mocking utility for unit tests (#1858) 2023-12-01 19:17:46 +00:00
user Merge branch 'rebase-v1.21/forgejo-branding' into wip-v1.21-forgejo 2023-11-13 16:47:18 +01:00
webhook Fix comment permissions (#28213) (#28216) 2023-11-26 13:56:50 +01: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 Refactor system setting (#27000) (#27452) 2023-10-05 10:37:59 +00:00
repo_test.go
repo_transfer.go [MODERATION] User blocking 2023-11-13 13:58:02 +01:00
repo_transfer_test.go [MODERATION] User blocking 2023-11-13 13:58:02 +01:00