3 Commits (f4c1f43644eb4a30d185518c1732b24aa821e39d)

Author	SHA1	Message	Date
wxiaoguang	cea9401634	Following-up improvments for various PRs (#25620) ... For: * #22743 * #25408 * #25412 * #25588	1 year ago
Lunny Xiao	65acd1e9ef	Fix branch commit message too long problem (#25588) ... When branch's commit CommitMessage is too long, the column maybe too short.(TEXT 16K for mysql). This PR will fix it to only store the summary because these message will only show on branch list or possible future search?	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