summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add v1.21.0 changelog (#28005) (#28048)v1.21.0Denys Konovalov2023-11-141-1/+448
| | | | | | | | | Backport changelog for v1.21.0 as Giteabot doesn't seem to be in the mood for it --------- Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: silverwind <me@silverwind.io>
* enable system users for comment.LoadPoster (#28014) (#28032)Giteabot2023-11-142-1/+38
| | | | | | | | | | | | | | | | Backport #28014 by @earl-warren System users (Ghost, ActionsUser, etc) have a negative id and may be the author of a comment, either because it was created by a now deleted user or via an action using a transient token. The GetPossibleUserByID function has special cases related to system users and will not fail if given a negative id. Refs: https://codeberg.org/forgejo/forgejo/issues/1425 (cherry picked from commit 6a2d2fa24390116d31ae2507c0a93d423f690b7b) Co-authored-by: Earl Warren <109468362+earl-warren@users.noreply.github.com>
* Fix viewing wiki commit on empty repo (#28040) (#28044)Giteabot2023-11-141-1/+0
| | | | | | | | | Backport #28040 by @JakobDev Fixes https://codeberg.org/forgejo/forgejo/issues/1758 For some weird reason we need to cast this nil. Co-authored-by: JakobDev <jakobdev@gmx.de>
* Add word break to the repo list in admin settings page (#28034) (#28035)Giteabot2023-11-141-2/+2
| | | | | | | | | | | | | Backport #28034 by @yp05327 Before: ![image](https://github.com/go-gitea/gitea/assets/18380374/ed464937-e20d-4f5b-b997-e86c2d96469d) After: ![image](https://github.com/go-gitea/gitea/assets/18380374/471e77b3-516e-4ae9-b901-0cf8745eb9aa) Co-authored-by: yp05327 <576951401@qq.com>
* fixed duplicate attachments on dump on windows (#28019) (#28031)Giteabot2023-11-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | Backport #28019 by @anudeepreddy Hi, This PR fixes #27988. The use of `path.join`(which uses `/` as the file separator) to construct paths and comparing them with paths constructed using `filepath.join`(which uses platform specific file separator) is the root cause of this issue. The desired behavior is to ignore attachments when dumping data directory. Due to the what's mentioned above, the function `addRecursiveExclude` is not actually ignoring the attachments directory and is being written to the archive. The attachment directory is again added to the archive (with different file separator as mentioned in the issue) causing a duplicate entry on windows. The solution is to use `filepath.join` in `addResursiveExclude` to construct `currentAbsPath`. Co-authored-by: Anudeep Reddy <anudeepc85@gmail.com>
* Dont leak private users via extensions (#28023) (#28029)Giteabot2023-11-141-0/+5
| | | | | | Backport #28023 by @6543 there was no check in place if a user could see a other user, if you append e.g. `.rss`
* Change default size of issue/pr attachments and repo file (#27946) (#28017)Giteabot2023-11-133-8/+8
| | | | | | | | Backport #27946 by @lng2020 As title. Some attachments and file sizes can easily be larger than these limits Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Fix wrong xorm Delete usage(backport for 1.21) (#28002)Nanguan Lin2023-11-121-1/+1
| | | | | manually backport for https://github.com/go-gitea/gitea/pull/27995 The conflict is `ctx` and `db.Defaultctx`.
* Move some JS code from `fomantic.js` to standalone files (#27994) (#28001)Giteabot2023-11-128-93/+100
| | | | | | | | | | | | | | | Backport #27994 by @wxiaoguang To improve maintainability, this PR: 1. Rename `web_src/js/modules/aria` to `web_src/js/modules/fomantic` (the code there are all for aria of fomantic) 2. Move api/transition related code to `web_src/js/modules/fomantic/api.js` and `web_src/js/modules/fomantic/transition.js` No logic is changed. Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Render email addresses as such if followed by punctuation (#27987) (#27992)Giteabot2023-11-112-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | Backport #27987 by @yardenshoham Added the following characters to the regular expression for the email: - , - ; - ? - ! Also added a test case. - Fixes #27616 # Before ![image](https://github.com/go-gitea/gitea/assets/20454870/c57eac26-f281-43ef-a51d-9c9a81b63efa) # After ![image](https://github.com/go-gitea/gitea/assets/20454870/fc7d5c08-4350-4af0-a7f0-d1444d2d75af) Signed-off-by: Yarden Shoham <git@yardenshoham.com> Co-authored-by: Yarden Shoham <git@yardenshoham.com>
* Show error toast when file size exceeds the limits (#27985) (#27986)Giteabot2023-11-101-0/+4
| | | | | | | | | | | Backport #27985 by @lng2020 As title. Before that, there was no alert at all. After: ![error_toast](https://github.com/go-gitea/gitea/assets/70063547/c54ffeed-76f8-4c3a-b5dc-b9b3e0f8fc76) Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Fix citation error when the file size is larger than 1024 bytes (#27958) ↵Giteabot2023-11-081-5/+2
| | | | | | | | | | | | (#27965) Backport #27958 by @yp05327 Mentioned in: https://github.com/go-gitea/gitea/pull/27931#issuecomment-1798016960 Same to #25131, so use the same method to fix this problem. Co-authored-by: yp05327 <576951401@qq.com>
* Add word-break to repo description in home page (#27924) (#27957)Giteabot2023-11-082-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | Backport #27924 by @yp05327 In #25315, @denyskon fixed UI on mobile view. But for the repo description, on desktop view there's no word-break. So maybe we can just add `gt-word-break` to fix it on both mobile view and desktop view. Before: desktop view: ![image](https://github.com/go-gitea/gitea/assets/18380374/a7659f5b-fbe9-400a-8cc2-cca44778556e) mobile view: ![image](https://github.com/go-gitea/gitea/assets/18380374/611f1b81-58ac-4213-b165-5c73e24ca79e) After: desktop view: ![image](https://github.com/go-gitea/gitea/assets/18380374/f21bf3a7-f6aa-457d-9bfa-5c57659c68b1) mobile view(almost same?) ![image](https://github.com/go-gitea/gitea/assets/18380374/ad2d1a4d-1172-402c-b5fc-5e910657847d) Co-authored-by: yp05327 <576951401@qq.com> Co-authored-by: silverwind <me@silverwind.io>
* Document REACTION_MAX_USER_NUM setting option (#27954) (#27959)Giteabot2023-11-082-0/+4
| | | | | | | | | | Backport #27954 by @6543 as title --- *Sponsored by Kithara Software GmbH* Co-authored-by: 6543 <m.huber@kithara.com>
* Fix rendering assignee changed comments without assignee (#27927) (#27952)Giteabot2023-11-071-24/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport #27927 by @invliD When an assignee changed event comment is rendered, most of it is guarded behind the assignee ID not being 0. However, if it is 0, that results in quite broken rendering for that comment and the next one. This can happen, for example, when repository data imported from outside of Gitea is incomplete. This PR makes sure comments with an assignee ID of 0 are not rendered at all. --- Screenshot before: <img width="272" alt="Bildschirm­foto 2023-11-05 um 20 12 18" src="https://github.com/go-gitea/gitea/assets/42910/7d629d76-fee4-4fe5-9e3a-bf524050cead"> The comments in this screenshot are: 1. A regular text comment 2. A user being unassigned 3. A user being assigned 4. The title of the PR being changed Comments 2 and 3 are rendered without any text, which indents the next comment and does not leave enough vertical space. Co-authored-by: Sebastian Brückner <code@nik.dev>
* Add word break to release title (#27942) (#27947)Giteabot2023-11-071-1/+1
| | | | | | | | | | | | | Backport #27942 by @yp05327 Before: ![image](https://github.com/go-gitea/gitea/assets/18380374/74c925e0-15ae-4602-8b56-0b69f54a5e7a) After: ![image](https://github.com/go-gitea/gitea/assets/18380374/027c34ef-0cbc-4156-a198-44bf5dd924e2) Co-authored-by: yp05327 <576951401@qq.com>
* Update environment-to-ini flag parsing (#27914) (#27940)Giteabot2023-11-061-12/+16
| | | | | | | | | | | | Backport #27914 by @fashberg This Fixes #27913 This commit updates `environment-to-ini` to be compatible with update urfave/cli/v2 Doc: <https://cli.urfave.org/v2/examples/combining-short-options/> Co-authored-by: Folke <folke@ashberg.de>
* Unify two factor check (#27915) (#27929)Giteabot2023-11-064-65/+77
| | | | | | | | | | | | Backport #27915 by @KN4CK3R Fixes #27819 We have support for two factor logins with the normal web login and with basic auth. For basic auth the two factor check was implemented at three different places and you need to know that this check is necessary. This PR moves the check into the basic auth itself. Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Remove `known issue` section in Gitea Actions Doc (#27930) (#27938)Giteabot2023-11-062-62/+0
| | | | | | | | | | | Backport #27930 by @lng2020 The bug has been fixed for several months in the `docker/build-push-action` The fix commit is [d8823bfaed](https://github.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba) as the Gitea Actions Doc mentioned too. Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Fix JS NPE when viewing specific range of PR commits (#27912) (#27923)Giteabot2023-11-061-1/+1
| | | | | | | | | Backport #27912 by @delvh This should be the easiest fix. While other solutions might be possible that exterminate the root cause, they will not be as trivial. Co-authored-by: delvh <dev.lh@web.de>
* Install poetry dependencies with --no-root (#27919) (#27920)Giteabot2023-11-061-1/+1
| | | | | | | | | | | | Backport #27919 by @silverwind Poetry 1.7.0 or higher will print a warning otherwise, see discussions: https://github.com/python-poetry/poetry/pull/8369 https://github.com/python-poetry/poetry/issues/1132 > --no-root Do not install the root package (the current project). Co-authored-by: silverwind <me@silverwind.io>
* Show correct commit sha when viewing single commit diff (#27916) (#27921)Giteabot2023-11-061-1/+1
| | | | | | | | | | Backport #27916 by @sebastian-sauer Show the correct sha when viewing a single commit. ![image](https://github.com/go-gitea/gitea/assets/1135157/5f39a84e-11ed-4700-b40b-eb9da6e91bec) Co-authored-by: sebastian-sauer <sauer.sebastian@gmail.com>
* Fix 500 when deleting a dismissed review (#27903) (#27910)Giteabot2023-11-052-0/+40
| | | | | | | | Backport #27903 by @lng2020 Fix #27767 Add a test to ensure its behavior Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Remove action runners on user deletion (#27902) (#27908)Giteabot2023-11-053-0/+33
| | | | | | | | | | | | | Backport #27902 by @earl-warren - On user deletion, delete action runners that the user has created. - Add a database consistency check to remove action runners that have nonexistent belonging owner. - Resolves https://codeberg.org/forgejo/forgejo/issues/1720 (cherry picked from commit 009ca7223dab054f7f760b7ccae69e745eebfabb) Co-authored-by: Earl Warren <109468362+earl-warren@users.noreply.github.com> Co-authored-by: Gusted <postmaster@gusted.xyz>
* Backport translations to v1.21 (#27899)Denys Konovalov2023-11-0427-5956/+3548
| | | | I manually fixed most of the files so that used translation keys don't get deleted.
* Remove set tabindex on view issue (#27892) (#27896)Giteabot2023-11-032-7/+7
| | | | | | | | | | | Backport #27892 by @earl-warren - Remove the set tabindex and instead let the browser figure out the correct tab order. - Resolves https://codeberg.org/forgejo/forgejo/issues/1626 Co-authored-by: Earl Warren <109468362+earl-warren@users.noreply.github.com> Co-authored-by: Gusted <postmaster@gusted.xyz> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix DownloadFunc when migrating releases (#27887) (#27890)Giteabot2023-11-032-6/+9
| | | | | | | | | | | | | Backport #27887 by @Zettat123 We should not use `asset.ID` in DownloadFunc because DownloadFunc is a closure. https://github.com/go-gitea/gitea/blob/1bf5527eac6b947010c8faf408f6747de2a2384f/services/migrations/gitea_downloader.go#L284-L295 A similar bug when migrating from GitHub has been fixed in #14703. This PR fixes the bug when migrating from Gitea and GitLab. Co-authored-by: Zettat123 <zettat123@gmail.com>
* Fix http protocol auth (#27875) (#27876)Giteabot2023-11-024-14/+47
| | | | | Backport #27875 by @lunny Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Reduce margin/padding on flex-list items and divider (#27872) (#27874)Giteabot2023-11-022-3/+3
| | | | | | Backport #27872 by @silverwind Small CSS tweak, reduces margin/padding from 14px to 10px, which I think looks better
* refactor postgres connection string building (#27723) (#27869)Giteabot2023-11-013-30/+47
| | | | | | | | | | | | Backport #27723 by @mpldr This patchset changes the connection string builder to use net.URL and the host/port parser to use the stdlib function for splitting host from port. It also adds a footnote about a potentially required portnumber for postgres UNIX sockets. Fixes: #24552 Co-authored-by: Moritz Poldrack <33086936+mpldr@users.noreply.github.com>
* Change katex limits (#27823) (#27868)Giteabot2023-11-011-2/+12
| | | | | | | | | | | | Backport #27823 by @KN4CK3R Fixes #27812 Use higher defaults again but limit the input size. ![grafik](https://github.com/go-gitea/gitea/assets/1666336/23cdf572-de30-4799-b9cf-ef386b1623b9) Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* doc: actions/act-runner: document running as a systemd service (#27844) (#27866)Giteabot2023-11-011-0/+34
| | | | | | | | Backport #27844 by @nodiscc This documents running `act-runner` as a systemd service under a dedicated user account. Co-authored-by: nodiscc <nodiscc@gmail.com>
* Delete repos of org when purge delete user (#27273) (#27728)65432023-11-0114-51/+79
| | | | | | | | | Fixes https://codeberg.org/forgejo/forgejo/issues/1514 Backports #27273 --------- Co-authored-by: JakobDev <jakobdev@gmx.de>
* Clean up template locale usage (#27856) (#27857)wxiaoguang2023-10-3110-65/+33
| | | | | | | Backport #27856 The only conflict is `ThemeName` in `500.tmpl`, it has been resolved manually by keeping using old `{{.SignedUser.Theme}}{{else}}{{DefaultTheme}}`
* Fix package webhook (#27839) (#27855)Giteabot2023-10-3114-1/+97
| | | | | | | | Backport #27839 by @lunny Fix #23742 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Add user secrets API integration tests (#27832) (#27852)Giteabot2023-10-311-0/+98
| | | | | | | | Backport #27832 by @jbgomond Adds the missing user secrets API integration tests so #27829 does not happen again Co-authored-by: Jean-Baptiste Gomond <dev@jbgomond.com>
* Fix wrong relative path on obtain token from command line (#27850) (#27851)Giteabot2023-10-312-1/+3
| | | | | | | Backport #27850 by @lunny Caused by #27845 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* doc: actions/act-runner: document obtaining a runner registration token from ↵Giteabot2023-10-301-0/+6
| | | | gitea CLI (#27845) (#27848)
* Fix/upload artifact error windows (#27802) (#27840)Giteabot2023-10-301-1/+2
|
* Always use whole user name as link (#27815) (#27838)Giteabot2023-10-301-5/+1
| | | | | | | | | | | | | | | | | Backport #27815 by @denyskon Starting from #25790 this shared template only linked the username of the user if both display name and username were shown. I experienced myself always trying to click on the display name - I think it is annoying for others too. After: ![grafik](https://github.com/go-gitea/gitea/assets/47871822/a0e82127-b773-4ca4-890f-d18422a7bef2) ![grafik](https://github.com/go-gitea/gitea/assets/47871822/79efcf93-2f50-4fc4-ba15-afc6174be48c) Co-authored-by: Denys Konovalov <kontakt@denyskon.de>
* Fix bad method call when deleting user secrets via API (#27829) (#27831)Giteabot2023-10-291-1/+1
| | | | | | | | | Backport #27829 by @jbgomond Fixed a little mistake when you deleting user secrets via the API. Found it when working on #27725. It should be backported to 1.21 I think. Co-authored-by: Jean-Baptiste Gomond <dev@jbgomond.com>
* Dockerfile small refactor (#27757) (#27826)Giteabot2023-10-293-24/+54
| | | | | | | | Backport #27757 by @nfsec - Size and layer optimization, - Maintaining consistency in definitions (comments, apk etc.), Co-authored-by: Patryk Krawaczyński <nfsec@users.noreply.github.com>
* Upgrade xorm to 1.3.4 (#27807) (#27813)Giteabot2023-10-273-4/+4
| | | | | | | | | | | Backport #27807 by @lng2020 Noticeable change: Remove the `OrderBy("1") ` [patch](https://github.com/go-gitea/gitea/pull/27673#issuecomment-1768570142) for mssql since xorm has [fixed it](https://gitea.com/xorm/xorm/commit/0f085408afd85707635eadb2294ab52be04f3c0f). Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Chroma v2.10.0 (#27803) (#27805)Giteabot2023-10-272-3/+3
| | | | | | | | | | | Backport #27803 by @bt90 Bump the chroma version to v2.10.0: https://github.com/alecthomas/chroma/releases/tag/v2.10.0 This release includes a better Java lexer https://github.com/alecthomas/chroma/pull/873 Co-authored-by: bt90 <btom1990@googlemail.com>
* Add dedicated class for empty placeholders (#27788) (#27792)Giteabot2023-10-263-6/+8
| | | | | | | | | | | | | Backport #27788 by @silverwind Fixes: https://github.com/go-gitea/gitea/issues/27784 <img width="1033" alt="Screenshot 2023-10-25 at 19 07 15" src="https://github.com/go-gitea/gitea/assets/115237/1a363851-1a86-48cb-99ec-0a573371bb6e"> <img width="1051" alt="Screenshot 2023-10-25 at 19 07 41" src="https://github.com/go-gitea/gitea/assets/115237/add4b606-2264-430a-af35-249ef005817f"> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Close all hashed buffers (#27787) (#27790)Giteabot2023-10-254-1/+19
| | | | | | | | Backport #27787 by @KN4CK3R Add missing `.Close()` calls. The current code does not delete the temporary files if the data grows over 32mb. Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Add gap between diff boxes (#27776) (#27781)Giteabot2023-10-251-0/+3
| | | | | | | | | | | | | Backport #27776 by @silverwind Before (almost no gap between files): <img width="1240" alt="Screenshot 2023-10-24 at 19 43 32" src="https://github.com/go-gitea/gitea/assets/115237/30cdbdbc-d102-479c-89ce-3f68837ae0cd"> After (with 8px gap): <img width="1241" alt="Screenshot 2023-10-24 at 19 43 22" src="https://github.com/go-gitea/gitea/assets/115237/72b26a30-8730-4a36-8de9-be143b684b98"> Co-authored-by: silverwind <me@silverwind.io>
* Do not force creation of _cargo-index repo on publish (#27266) (#27765)Giteabot2023-10-243-7/+13
| | | | | | | | | | | | | | | | | | | | | | | Backport #27266 by @merlleu Hello there, Cargo Index over HTTP is now prefered over git for package updates: we should not force users who do not need the GIT repo to have the repo created/updated on each publish (it can still be created in the packages settings). The current behavior when publishing is to check if the repo exist and create it on the fly if not, then update it's content. Cargo HTTP Index does not rely on the repo itself so this will be useless for everyone not using the git protocol for cargo registry. This PR only disable the creation on the fly of the repo when publishing a crate. This is linked to #26844 (error 500 when trying to publish a crate if user is missing write access to the repo) because it's now optional. Co-authored-by: merlleu <r.langdorph@gmail.com> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Fix incorrect "tab" parameter for repo search sub-template (#27755) (#27764)Giteabot2023-10-241-2/+2
| | | | | Backport #27755 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* fix issues in translation file (#27699) (#27737)Denys Konovalov2023-10-241-11/+9
| | | | | | | Backport #27699 - use correct comment sign for INI (`;`) - remove duplicated `repo.branch.search` key - remove duplicated spaces & similar
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-06 03:05:20 +0000