summaryrefslogtreecommitdiffstats
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
* Fix index too many file names bug (#31903) (#31953)Lunny Xiao2024-09-031-9/+32
| | | | | Try to fix #31884 Fix #28584 Backport #31903
* Upgrade bleve to 2.4.2 (#31894)Lunny Xiao2024-08-211-1/+1
| | | backport #31762
* Refactor the usage of batch catfile (#31754) (#31889)Giteabot2024-08-2115-90/+201
| | | | | | | | | | | | | | Backport #31754 by @lunny When opening a repository, it will call `ensureValidRepository` and also `CatFileBatch`. But sometimes these will not be used until repository closed. So it's a waste of CPU to invoke 3 times git command for every open repository. This PR removed all of these from `OpenRepository` but only kept checking whether the folder exists. When a batch is necessary, the necessary functions will be invoked. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Fix raw wiki links (#31825) (#31845)Giteabot2024-08-173-22/+16
| | | | | | | | | | | | | | | | | | | | | Backport #31825 by @Zettat123 Fix #31395 This regression is introduced by #30273. To find out how GitHub handles this case, I did [some tests](https://github.com/go-gitea/gitea/issues/31395#issuecomment-2278929115). I use redirect in this PR instead of checking if the corresponding `.md` file exists when rendering the link because GitHub also uses redirect. With this PR, there is no need to resolve the raw wiki link when rendering a wiki page. If a wiki link points to a raw file, access will be redirected to the raw link. --------- Co-authored-by: Zettat123 <zettat123@gmail.com> Co-authored-by: yp05327 <576951401@qq.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Fix `IsObjectExist` with gogit (#31790) (#31806)Giteabot2024-08-094-10/+121
| | | | | | | | | | | | | | | | Backport #31790 by @wolfogre Fix #31271. When gogit is enabled, `IsObjectExist` calls `repo.gogitRepo.ResolveRevision`, which is not correct. It's for checking references not objects, it could work with commit hash since it's both a valid reference and a commit object, but it doesn't work with blob objects. So it causes #31271 because it reports that all blob objects do not exist. Co-authored-by: Jason Song <i@wolfogre.com>
* Fix protected branch files detection on pre_receive hook (#31778) (#31796)Giteabot2024-08-084-7/+74
| | | | | | | | | | | | | | | | | | | Backport #31778 by @lunny Fix #31738 When pushing a new branch, the old commit is zero. Most git commands cannot recognize the zero commit id. To get the changed files in the push, we need to get the first diverge commit of this branch. In most situations, we could check commits one by one until one commit is contained by another branch. Then we will think that commit is the diverge point. And in a pre-receive hook, this will be more difficult because all commits haven't been merged and they actually stored in a temporary place by git. So we need to bring some envs to let git know the commit exist. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Add `TAGS` to `TEST_TAGS` and fix bugs found with gogit (#31791) (#31795)Giteabot2024-08-072-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | Backport #31791 by @wolfogre Found at https://github.com/go-gitea/gitea/pull/31790#issuecomment-2272898915 `unit-tests-gogit` never work since the workflow set `TAGS` with `gogit`, but the Makefile use `TEST_TAGS`. <img width="690" alt="image" src="https://github.com/user-attachments/assets/fb68df49-952b-42b9-8438-44200cefff43"> ![image](https://github.com/user-attachments/assets/78ff88c7-3b5f-4d50-9c58-e607bf7b1a71) This PR adds the values of `TAGS` to `TEST_TAGS`, ensuring that setting `TAGS` is always acceptable and avoiding confusion about which one should be set. After this PR: <img width="714" alt="image" src="https://github.com/user-attachments/assets/54cc7f38-d95b-4dbc-a87c-daba63462b86"> Co-authored-by: Jason Song <i@wolfogre.com>
* Distinguish LFS object errors to ignore missing objects during migration ↵Giteabot2024-07-313-4/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#31702) (#31745) Backport #31702 by @wolfogre Fix #31137. Replace #31623 #31697. When migrating LFS objects, if there's any object that failed (like some objects are losted, which is not really critical), Gitea will stop migrating LFS immediately but treat the migration as successful. This PR checks the error according to the [LFS api doc](https://github.com/git-lfs/git-lfs/blob/main/docs/api/batch.md#successful-responses). > LFS object error codes should match HTTP status codes where possible: > > - 404 - The object does not exist on the server. > - 409 - The specified hash algorithm disagrees with the server's acceptable options. > - 410 - The object was removed by the owner. > - 422 - Validation error. If the error is `404`, it's safe to ignore it and continue migration. Otherwise, stop the migration and mark it as failed to ensure data integrity of LFS objects. And maybe we should also ignore others errors (maybe `410`? I'm not sure what's the difference between "does not exist" and "removed by the owner".), we can add it later when some users report that they have failed to migrate LFS because of an error which should be ignored. Co-authored-by: Jason Song <i@wolfogre.com>
* Properly filter issue list given no assignees filter (#31522) (#31685)Giteabot2024-07-242-1/+12
| | | | | | | Backport #31522 by @kemzeb Quick fix #31520. This issue is related to #31337. Co-authored-by: Kemal Zebari <60799661+kemzeb@users.noreply.github.com>
* Fix slow patch checking with commits that add or remove many files (#31548) ↵Giteabot2024-07-051-8/+27
| | | | | | | | | | | | | | | | | | | (#31560) Backport #31548 by @brechtvl Running git update-index for every individual file is slow, so add and remove everything with a single git command. When such a big commit lands in the default branch, it could cause PR creation and patch checking for all open PRs to be slow, or time out entirely. For example, a commit that removes 1383 files was measured to take more than 60 seconds and timed out. With this change checking took about a second. This is related to #27967, though this will not help with commits that change many lines in few files. Co-authored-by: Brecht Van Lommel <brecht@blender.org>
* remove typo (#31524)rayden842024-06-291-2/+2
|
* Support relative paths to videos from Wiki pages (#31061) (#31453)Giteabot2024-06-223-43/+83
| | | | | | | | | | | | | | | | | | | Backport #31061 by @sergeyvfx This change fixes cases when a Wiki page refers to a video stored in the Wiki repository using relative path. It follows the similar case which has been already implemented for images. Test plan: - Create repository and Wiki page - Clone the Wiki repository - Add video to it, say `video.mp4` - Modify the markdown file to refer to the video using `<video src="video.mp4">` - Commit the Wiki page - Observe that the video is properly displayed Co-authored-by: Sergey Sharybin <sergey.vfx@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix markdown math brackets render problem (#31420) (#31430)Giteabot2024-06-202-1/+9
| | | | | | Backport #31420 by charles7668 Co-authored-by: charles <30816317+charles7668@users.noreply.github.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Increase max length of org team names from 30 to 255 characters (#31410) ↵Giteabot2024-06-201-2/+2
| | | | | | | | | | | (#31421) Backport #31410 by tobiasbp This PR modifies the structs for editing and creating org teams to allow team names to be up to 255 characters. The previous maximum length was 30 characters. Co-authored-by: Tobias Balle-Petersen <tobias.petersen@unity3d.com>
* Fix rendered wiki page link (#31398) (#31407)wxiaoguang2024-06-198-71/+55
| | | | | Backport #31398 Fix #31395
* Fix bug filtering issues which have no project (#31337) (#31367)Lunny Xiao2024-06-171-1/+6
|
* Fix natural sort (#31384) (#31394)Giteabot2024-06-172-17/+87
| | | | | | | Backport #31384 by wxiaoguang Fix #31374 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix missing images in editor preview due to wrong links (#31299) (#31393)wxiaoguang2024-06-172-6/+8
| | | | | | | | | | | | Backport #31299 Parse base path and tree path so that media links can be correctly created with /media/. Resolves #31294 --------- Co-authored-by: Brecht Van Lommel <brecht@blender.org>
* Fix duplicate sub-path for avatars (#31365) (#31368)wxiaoguang2024-06-152-13/+25
| | | Backport #31365, only backport necessary changes.
* Backport Iif (#31353)wxiaoguang2024-06-132-2/+70
|
* Fix hash render end with colon (#31319) (#31346)Giteabot2024-06-132-1/+2
| | | | | | | | Backport #31319 by @lunny Fix a hash render problem like `<hash>: xxxxx` which is usually used in release notes. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Fix adopt repository has empty object name in database (#31333) (#31335)Giteabot2024-06-121-0/+1
| | | | | | | | | | | Backport #31333 by @lunny Fix #31330 Fix #31311 A workaround to fix the old database is to update object_format_name to `sha1` if it's empty or null. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Fix #31185 try fix lfs download from bitbucket failed (#31201) (#31329)Giteabot2024-06-125-5/+8
| | | | | | | Backport #31201 by @Zoupers Fix #31185 Co-authored-by: Zoupers Zou <1171443643@qq.com>
* Delete legacy cookie before setting new cookie (#31306) (#31317)Giteabot2024-06-111-4/+4
| | | | | Backport #31306 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Remove sub-path from container registry realm (#31293) (#31300)Giteabot2024-06-102-7/+4
| | | | | Backport #31293 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Make blockquote attention recognize more syntaxes (#31240) (#31250)Giteabot2024-06-043-19/+86
| | | | | | | Backport #31240 by wxiaoguang Fix #31214 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Make pasted "img" tag has the same behavior as markdown image (#31235) (#31243)Giteabot2024-06-044-59/+75
| | | | | | | | | | Backport #31235 by wxiaoguang Fix #31230 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Split sanitizer functions and fine-tune some tests (#31192) (#31200)Giteabot2024-05-318-245/+270
| | | | | Backport #31192 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix missing memcache import (#31105) (#31109)Giteabot2024-05-271-0/+2
| | | | | Backport #31105 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Make gitea webhooks openproject compatible (#28435) (#31081)Giteabot2024-05-263-0/+9
| | | | | Backport #28435 by Chief-Detektor Co-authored-by: André Rosenhammer <andre.rosenhammer@gmail.com>
* Support setting the `default` attribute of the issue template dropdown field ↵Giteabot2024-05-242-0/+117
| | | | | | | | | | | | | | (#31045) (#31059) Backport #31045 by @Zettat123 Fix #31044 According to [GitHub issue template documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#attributes-for-dropdown), the `default` attribute can be used to specify the preselected option for a dropdown field. Co-authored-by: Zettat123 <zettat123@gmail.com>
* Refactor sha1 and time-limited code (#31023) (#31030)Giteabot2024-05-214-87/+116
| | | | | Backport #31023 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix project column title overflow (#31011) (#31025)Giteabot2024-05-201-4/+5
| | | | | Backport #31011 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Improve reverse proxy documents and clarify the AppURL guessing behavior ↵Giteabot2024-05-192-17/+26
| | | | | | | | | | | | | | | (#31003) (#31020) Backport #31003 by wxiaoguang Fix #31002 1. Mention Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea 2. Clarify the basic requirements and move the "general configuration" to the top 3. Add a comment for the "container registry" 4. Use 1.21 behavior if the reverse proxy is not correctly configured Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Simplify mirror repository API logic (#30963) (#31009)Giteabot2024-05-181-1/+1
| | | | | | | Backport #30963 by wxiaoguang Fix #30921 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Always load or generate oauth2 jwt secret (#30942) (#30978)Giteabot2024-05-142-12/+33
| | | | | | | Backport #30942 by @wxiaoguang Fix #30923 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Support using label names when changing issue labels (#30943) (#30958)Giteabot2024-05-131-2/+3
| | | | | | | | | | | | | | | | Backport #30943 by @Zettat123 Resolve #30917 Make the APIs for adding labels and replacing labels support both label IDs and label names so the [`actions/labeler`](https://github.com/actions/labeler) action can work in Gitea. <img width="600px" src="https://github.com/go-gitea/gitea/assets/15528715/7835c771-f637-4c57-9ce5-e4fbf56fa0d3" /> Co-authored-by: Zettat123 <zettat123@gmail.com>
* Move database operations of merging a pull request to post receive hook and ↵Giteabot2024-05-082-0/+10
| | | | | | | | | | | | | | | | | | | | | add a transaction (#30805) (#30888) Backport #30805 by @lunny Merging PR may fail because of various problems. The pull request may have a dirty state because there is no transaction when merging a pull request. ref https://github.com/go-gitea/gitea/pull/25741#issuecomment-2074126393 This PR moves all database update operations to post-receive handler for merging a pull request and having a database transaction. That means if database operations fail, then the git merging will fail, the git client will get a fail result. There are already many tests for pull request merging, so we don't need to add a new one. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Refactor AppURL usage (#30885) (#30891)wxiaoguang2024-05-083-9/+112
| | | | | | | Backport #30885 Fix #30883 Fix #29591 Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Make sure git version&feature are always prepared (#30877) (#30879)wxiaoguang2024-05-0713-125/+94
| | | Backport #30877
* Make "sync branch" also sync object format and add tests (#30878) (#30880)Giteabot2024-05-073-27/+41
| | | | | Backport #30878 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix markdown URL parsing for commit ID (#30812) (#30855)Giteabot2024-05-044-74/+115
| | | | | Backport #30812 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix no edit history after editing issue's title and content (#30814) (#30845)Giteabot2024-05-031-1/+1
| | | | | | | | | Backport #30814 by @yp05327 Fix #30807 reuse functions in services Co-authored-by: yp05327 <576951401@qq.com>
* Improve grep search (#30843) (#30850)Giteabot2024-05-034-7/+59
| | | | | | | | Backport #30843 by wxiaoguang Reduce the context line number to 1, make "git grep" search respect the include/exclude patter, and fix #30785 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Skip gzip for some well-known compressed file types (#30796) (#30813)Giteabot2024-05-021-0/+8
| | | | | | Backport #30796 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: silverwind <me@silverwind.io>
* Fix markdown rendering when mentioning users (#30795) (#30810)Giteabot2024-05-024-10/+14
| | | | | Backport #30795 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix bleve fuzziness (#30799) (#30804)Giteabot2024-05-013-9/+15
| | | | | | | | Backport #30799 by wxiaoguang Fix #30797 Fix #30317 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix issue label rendering in the issue popup (#30763) (#30773)Giteabot2024-04-301-22/+17
| | | | | Backport #30763 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Add some tests to clarify the "must-change-password" behavior (#30693)wxiaoguang2024-04-271-1/+3
| | | | | | | | | | Follow #30472: When a user is created by command line `./gitea admin user create`: Old behavior before #30472: the first user (admin or non-admin) doesn't need to change password. Revert to the old behavior before #30472
* Update misspell to 0.5.1 and add `misspellings.csv` (#30573)silverwind2024-04-273-6/+6
| | | | | | Misspell 0.5.0 supports passing a csv file to extend the list of misspellings, so I added some common ones from the codebase. There is at least one typo in a API response so we need to decided whether to revert that and then likely remove the dict entry.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-05 00:57:49 +0000