gitea

Commit Graph

Author	SHA1	Message	Date
6543	7fbdb60fc1	Start to migrate from `util.OptionalBool` to `optional.Option[bool]` (#29329 ) just create transition helper and migrate two structs	9 months ago
Lunny Xiao	537fa69962	Second part of refactor `db.Find` (#28194 ) Continue of #27798 and move more functions to `db.Find` and `db.Count`.	11 months ago
Lunny Xiao	aeb383025f	Also sync DB branches on push if necessary (#28361 ) Fix #28056 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.	12 months ago
Lunny Xiao	47b878858a	Search branches (#27055 ) Resolve #25233 <img width="1315" alt="图片" src="https://github.com/go-gitea/gitea/assets/81045/3ba59b58-471a-4e1b-985c-87edac2268c0"> <img width="1297" alt="图片" src="https://github.com/go-gitea/gitea/assets/81045/b6caa12f-323b-4f70-9c44-ef91cb71a26c">	1 year ago
wxiaoguang	2aa6a785cf	Make FindBranches have stable result (#25631 ) See the comment	1 year ago
Lunny Xiao	807c9712ef	Get latest commit statuses from database instead of git data on dashboard for repositories (#25605 ) related #24638	1 year ago
Lunny Xiao	6e19484f4d	Sync branches into databases (#22743 ) Related #14180 Related #25233 Related #22639 Close #19786 Related #12763 This PR will change all the branches retrieve method from reading git data to read database to reduce git read operations. - [x] Sync git branches information into database when push git data - [x] Create a new table `Branch`, merge some columns of `DeletedBranch` into `Branch` table and drop the table `DeletedBranch`. - [x] Read `Branch` table when visit `code` -> `branch` page - [x] Read `Branch` table when list branch names in `code` page dropdown - [x] Read `Branch` table when list git ref compare page - [x] Provide a button in admin page to manually sync all branches. - [x] Sync branches if repository is not empty but database branches are empty when visiting pages with branches list - [x] Use `commit_time desc` as the default FindBranch order by to keep consistent as before and deleted branches will be always at the end. --------- Co-authored-by: Jason Song <i@wolfogre.com>	1 year ago

7 Commits (4eb86d68233241d53cff1009ecff17ac35efccd4)