gitea

Commit Graph

Author	SHA1	Message	Date
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

Author

SHA1

Message

Date

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

2 Commits (d26ec5f2eb74a6437f998ab0af2ae058a64e06a2)