Lunny Xiao
5454fdacd4
Use git model to detect whether branch exist instead of gitrepo method ( #35459 )
2025-10-25 10:08:25 -07:00
Lunny Xiao
17c8aa6587
Add rebase push display wrong comments bug ( #35560 )
...
Fix #35518
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
2025-10-03 15:16:17 -07:00
bytedream
3a37d63d61
Allow renaming/moving binary/LFS files in the UI ( #34350 )
...
Adds the ability to rename/move binary files like binary blobs or images
and files that are too large in the web ui.
This was purposed in #24722 , along with the ability edit images via an
upload of a new image, which I didn't implement here (could be done in a
separate PR).
Binary file content:
File too large:
GitHub does the same (I've copied the text from there):
2025-06-16 17:15:07 -07:00
Lunny Xiao
c27d87a9ac
Refactor Branch struct in package modules/git ( #33980 )
...
The `Branch` struct in `modules/git` package is unnecessary. We can just
use a `string` to represent a branch
2025-04-02 17:31:32 +00:00
Lunny Xiao
42090844ed
Fix bug on action list deleted branch ( #32848 )
...
Fix
https://github.com/go-gitea/gitea/issues/32761#issuecomment-2540946064
---------
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
2024-12-16 05:38:39 +08:00
yp05327
daf2a4c047
Fix wrong display of recently pushed notification ( #25812 )
...
There's a bug in #25715 :
If user pushed a commit into another repo with same branch name, the
no-related repo will display the recently pushed notification
incorrectly.
It is simple to fix this, we should match the repo id in the sql query.
The latest commit is 2 weeks ago.
The notification comes from another repo with same branch name:
After:
In forked repo:
New PR Link will redirect to the original repo:
In the original repo:
New PR Link:
In the same repo:
New PR Link:
08/15 Update:
Follow #26257 , added permission check and logic fix mentioned in
https://github.com/go-gitea/gitea/pull/26257#discussion_r1294085203
2024/04/25 Update:
Fix #30611
---------
Co-authored-by: silverwind <me@silverwind.io >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com >
2024-05-21 17:00:35 +00:00
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 >
2023-06-29 10:03:20 +00:00
