gitea

Commit Graph

Author	SHA1	Message	Date
Giteabot	6f5748c507	Prevent update pull refs manually and will not affect other refs update (#31931 ) (#31955 ) Backport #31931 by @lunny All refs under `refs/pull` should only be changed from Gitea inside but not by pushing from outside of Gitea. This PR will prevent the pull refs update but allow other refs to be updated on the same pushing with `--mirror` operations. The main changes are to add checks on `update` hook but not `pre-receive` because `update` will be invoked by every ref but `pre-receive` will revert all changes once one ref update fails. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	6 months ago
Giteabot	e8c776c793	Fix push multiple branches error with tests (#31151 ) (#31153 ) Backport #31151 by @lunny Fix #31140 The previous logic is wrong when pushing multiple branches. After first branch updated, it will ignore left other branches sync operations. As a workaround for the repositories, just push a new commit after the patch applied will fix the repositories status. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	9 months ago
Lunny Xiao	263a716cb5	Performance optimization for git push (#30104 ) Agit returned result should be from `ProcReceive` hook but not `PostReceive` hook. Then for all non-agit pull requests, it will not check the pull requests for every pushing `refs/pull/%d/head`.	10 months ago
Jason Song	f371f84fa3	Restore deleted branches when syncing (#29898 ) Regression of #29493. If a branch has been deleted, repushing it won't restore it. Lunny may have noticed that, but I didn't delve into the comment then overlooked it: https://github.com/go-gitea/gitea/pull/29493#discussion_r1509046867 The additional comments added are to explain the issue I found during testing, which are unrelated to the fixes.	11 months ago
Jason Song	5bdf805e05	Sync branches to DB immediately when handle git hook calling (#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>	12 months ago

5 Commits (a3c660f89a9e4a69d1c9b182c21ff0654bf07143)