| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Backport #31033
user should be a collaborator of the base repo to create a PR
|
|
|
|
|
|
|
| |
Backport #31712 by @lunny
Fix #31708
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
|
|
|
|
| |
A separate backport of #31695 for 1.22
Fix #31673
|
|
|
|
|
|
|
| |
Backport #31522 by @kemzeb
Quick fix #31520. This issue is related to #31337.
Co-authored-by: Kemal Zebari <60799661+kemzeb@users.noreply.github.com>
|
|
|
|
|
|
|
|
| |
Backport #31672 by @techknowlogick
This lets developers who have direnv enabled to load our nix flake
automatically when entering it
Co-authored-by: techknowlogick <techknowlogick@gitea.com>
|
|
|
|
|
|
| |
fix https://github.com/go-gitea/gitea/issues/31658
backports #31662
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31659 by @Zettat123
Fix #31599
Fix #31472
A branch divergence is counted based on the default branch. If the
default branch is updated, all divergence caches of the repo need to be
deleted.
Co-authored-by: Zettat123 <zettat123@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31637 by @silverwind
Fixes: https://github.com/go-gitea/gitea/issues/31636
1. Issue sidebar topic is disussed in
https://github.com/go-gitea/gitea/issues/31636
2. Org description already has `overflow-wrap: anywhere` to ensure no
overflow.
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31564 by @tobiasbp
Gitea 1.22.1 was supposed to allow for team names of length 255 (up from
30) after the following PR was merged in:
https://github.com/go-gitea/gitea/pull/31410. However, the length of
team names was still limited to 30 as described in this issue:
https://github.com/go-gitea/gitea/issues/31554.
One more change to _gitea_ needs to be made to allow for the longer team
names, as there is a 30 character limit here:
https://github.com/go-gitea/gitea/blob/2c92c7c5226e29636a1d47a277130f477fa2037b/services/forms/org.go#L65
This PR changes that value to 255.
Co-authored-by: Tobias Balle-Petersen <tobias.petersen@unity3d.com>
|
|
|
| |
Fix #31182
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#31567)
Backport #31187
Resolves #31167.
https://github.com/go-gitea/gitea/pull/30885 changed the behavior of
`repo.AvatarLink()` where it can now take the empty string and append it
to the app data URL. This does not point to a valid avatar image URL,
and, as the issue mentions, previous Gitea versions returned the empty
string.
Co-authored-by: Kemal Zebari <60799661+kemzeb@users.noreply.github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#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>
|
|
|
|
| |
Co-authored-by: Lauris BH <lauris@nix.lv>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
|
| |
|
| |
|
|
|
|
|
| |
Backport #31506 by charles7668
Co-authored-by: charles <30816317+charles7668@users.noreply.github.com>
|
|
|
|
|
| |
Backport #31487 by CyberFlameGO
Co-authored-by: CyberFlame <cyberflameu@gmail.com>
|
| |
|
|
|
| |
Fix #31485
|
|
|
|
|
| |
Backport #31484 by brechtvl
Co-authored-by: Brecht Van Lommel <brecht@blender.org>
|
|
|
|
|
|
| |
Backport #31473 by brechtvl
Co-authored-by: Brecht Van Lommel <brecht@blender.org>
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31450 by @silverwind
See
https://docs.docker.com/reference/build-checks/legacy-key-value-format/.
Fixes these warnings seen during the docker build:
```
4 warnings found (use --debug to expand):
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 5)
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9)
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 75)
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 76)
```
Introduced in: https://github.com/moby/buildkit/pull/4923
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#31447) (#31466)
Backport #31447 by kiatt210
Fix #29065
Remove status filtering from GetUIDsAndNotificationCounts sql.
Co-authored-by: kiatt210 <40639725+kiatt210@users.noreply.github.com>
Co-authored-by: kiatt210 <kiatt210@github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
| |
backport #31400
|
|
|
|
|
|
|
| |
Backport #31445 by wxiaoguang
Fix #19031
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Backport #31432 by wxiaoguang
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#31431) (#31440)
Backport #31431 by @charles7668
close #31149
The problem is caused by the `data-query=` string affecting the parsing
of the `last_left` parameter. When the page is first rendered,
`data-query=` does not exist. However, after clicking expand, the
returned HTML contains this string, causing the line numbers to start
from 1 upon expanding a second time.
before fix

after fix

Co-authored-by: charles <30816317+charles7668@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
| |
Backport #31435 by brechtvl
It was correct only on the new issue page.
Resolves #31415
Co-authored-by: Brecht Van Lommel <brecht@blender.org>
|
|
|
|
|
| |
Backport #31428 by Sumit189
Co-authored-by: Sumit <sumit.18.paul@gmail.com>
|
|
|
|
|
|
| |
Backport #31420 by charles7668
Co-authored-by: charles <30816317+charles7668@users.noreply.github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
(#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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31419 by @silverwind
The avatar on "New Issue" and "New Pull Request" pages was inconsistent.
Removed the extra margin and the new CSS rules now use common parent
`<form id="#new-issue">` because `.repository.new.issue` is not present
on pull request page.
Before:
<img width="181" alt="Screenshot 2024-06-19 at 13 56 17"
src="https://github.com/go-gitea/gitea/assets/115237/5270d352-db5b-45b3-9d06-4790c17ae9b4">
<img width="213" alt="Screenshot 2024-06-19 at 13 54 02"
src="https://github.com/go-gitea/gitea/assets/115237/012f5607-aef0-4f48-90e3-8d4022480203">
After:
<img width="195" alt="Screenshot 2024-06-19 at 13 54 16"
src="https://github.com/go-gitea/gitea/assets/115237/e7590c66-3b28-4790-9970-33bd567eeb31">
<img width="212" alt="Screenshot 2024-06-19 at 13 54 22"
src="https://github.com/go-gitea/gitea/assets/115237/8e1cfede-614c-4cea-9af2-ada6da7a7361">
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
|
|
|
|
|
| |
Backport #31417 by @silverwind
Make `air` log less. Uses the option added in
https://github.com/air-verse/air/pull/367.
Co-authored-by: silverwind <me@silverwind.io>
|
|
|
|
|
| |
Backport #31398
Fix #31395
|
|
|
|
|
|
| |
Backport #31363 by silverwind
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Backport #31384 by wxiaoguang
Fix #31374
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Backport #31369 by Zettat123
Fix #31362
Co-authored-by: Zettat123 <zettat123@gmail.com>
|
|
|
| |
Backport #31365, only backport necessary changes.
|
|
|
|
| |
Fix #31376
Regression of #30395
|
| |
|
|
|
|
|
|
|
| |
Backport #31348 by @kerwin612
see: https://github.com/go-gitea/gitea/pull/29701/files#r1637325139
Co-authored-by: Kerwin Bryant <kerwin612@qq.com>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Backport #31341 by silverwind
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Backport #31281 by silverwind
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backport #31325 by @bohde
When using the MinIO storage driver for Actions Artifacts, we found that
the chunked artifact required significantly more memory usage to both
upload and merge than the local storage driver. This seems to be related
to hardcoding a value of `-1` for the size to the MinIO client [which
has a warning about memory usage in the respective
docs](https://pkg.go.dev/github.com/minio/minio-go/v7#Client.PutObject).
Specifying the size in both the upload and merge case reduces memory
usage of the MinIO client.
Co-authored-by: Rowan Bohde <rowan.bohde@gmail.com>
Co-authored-by: Kyle D <kdumontnu@gmail.com>
|
|
|
|
|
|
|
| |
Backport #31201 by @Zoupers
Fix #31185
Co-authored-by: Zoupers Zou <1171443643@qq.com>
|