gitea

Commit Graph

Author	SHA1	Message	Date
Giteabot	68bd1dd89d	Fix rename branch 500 when the target branch is deleted but exist in database (#30430 ) (#30437 ) Backport #30430 by @lunny Fix #30428 --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	10 months ago
Lunny Xiao	6e29242ebb	Fix schedule tasks bugs (#28691 ) (#28780 ) Fix #28157 Backport #28691 This PR fix the possible bugs about actions schedule. - Move `UpdateRepositoryUnit` and `SetRepoDefaultBranch` from models to service layer - Remove schedules plan from database and cancel waiting & running schedules tasks in this repository when actions unit has been disabled or global disabled. - Remove schedules plan from database and cancel waiting & running schedules tasks in this repository when default branch changed.	1 year ago
Lunny Xiao	87db4a47c8	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.	1 year ago
Zettat123	9a65d011f6	Some fixes of the prompt of new branches (#26257 ) Related to #26239 This PR makes some fixes: - do not show the prompt for mirror repos and repos with pull request units disabled - use `commit_time` instead of `updated_unix`, as `commit_time` is the real time when the branch was pushed	2 years ago
Zettat123	338d03ce2f	Only show newly pushed branches message in the same repository (#26148 ) Partly fixes #26130 This is a quick fix. #25812 will fully fix the bug.	2 years ago
Lunny Xiao	2f31d2d56c	Exclude default branch from pushed branch hint (#25795 ) When pushing to default branch, no pushing hint should be prompt. Fix #25778 --------- Co-authored-by: Giteabot <teabot@gitea.io>	2 years ago
Lunny Xiao	6375419468	Newly pushed branches hints on repository home page (#25715 ) This PR will display a pull request creation hint on the repository home page when there are newly created branches with no pull request. Only the recent 6 hours and 2 updated branches will be displayed. Inspired by #14003 Replace #14003 Resolves #311 Resolves #13196 Resolves #23743 co-authored by @kolaente	2 years ago
silverwind	88f835192d	Replace `interface{}` with `any` (#25686 ) Result of running `perl -p -i -e 's#interface\{\}#any#g' */` and `make fmt`. Basically the same [as golang did](`2580d0e08d`).	2 years ago
wxiaoguang	cea9401634	Following-up improvments for various PRs (#25620 ) For: * #22743 * #25408 * #25412 * #25588	2 years 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?	2 years 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>	2 years ago

11 Commits (c5f37af8cd7815d3a2602b0a55c80d28667f96ea)