1. Top
  2. gitea
  3. Commits
gitea

Development moved to Codeberg

Commits at b7abb31b7baeb2ee60d28b90354af3bef7f7a74a

  1. b7abb31b Move user password verification after checking his groups on ldap auth (#19587) In case the binded user can not access its own attributes. Signed-off-by: Gwilherm Folliot <gwilherm55fo@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Gwilherm Folliot authored at GitHub comitted at
  2. 772ad761 Fix some slice problems (incorrect slice length) (#19592) Lunny Xiao authored at GitHub comitted at
  3. c8ec2261 Fix sending empty notifications (#19589) - Don't send empty notifications on read notifications API. Gusted authored at GitHub comitted at
  4. 438646e0 Handle the error of a missing blob object fix #19530 (#19552) * Handle the error of a missing blob object * Show error in logs * as per @zeripath * Add missing error check * Add missing error check * Update compare.go * Use formal code * Update compare.go Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: techknowlogick <techknowlogick@gitea.io> 99rgosse authored at GitHub comitted at
  5. c18d8d69 Remove legacy `+build:` constraint (#19582) Go 1.17 and later use modern `//go:build` constraints, the old `// +build:` constraints should be removed. wxiaoguang authored at GitHub comitted at
  6. e2a3f3d2 Federation: return useful statistic information for nodeinfo (#19561) Add statistic information for total user count, active user count, issue count and comment count for `/nodeinfo` 6543 authored at GitHub comitted at
  7. 509d8112 Upgrade required git version to 2.0 (#19577) * Upgrade required git version to 2.0 * update document wxiaoguang authored at GitHub comitted at
  8. 0ba3ada8 add smtp password to install page (#17564) * add smtp password to install page * Update routers/install/install.go Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Vladimir Smagin authored at GitHub comitted at
  9. 71bafa02 ignore DNS error when doing migration allow/block check (#19566) Co-authored-by: 6543 <6543@obermui.de> wxiaoguang authored at GitHub comitted at
  10. 05234adf [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  11. d8905cb6 Dont overwrite err with nil & rename PullCheckingFuncs to reflect there usage (#19572) - dont overwrite err with nil unintentionaly - rename CheckPRReadyToMerge to CheckPullBranchProtections - rename prQueue to prPatchCheckerQueue from #9307 Co-authored-by: delvh <dev.lh@web.de> 6543 authored at GitHub comitted at
  12. 3725fa28 Improve UI on mobile (#19546) Start making the mobile experience not painful and be actually usable. This contains a few smaller changes to enhance this experience. - Submit buttons on the review forms aren't columns anymore and are now allowed to be displayed on one row. - The label/milestone & New Issue buttons were given each own row even tough, there's enough place to do it one the same row. This commit fixes that. - The issues+Pull tab on repo's has a third item besides the label/milestone & New Issue buttons, the search bar. On desktop there's enough place to do this on one row, for mobile it isn't, currently it was using for each item a new row. This commits fixes that by only giving the searchbar a new row and have the other two buttons on the same row. - The notification table will now be show a scrollbar instead of overflow. - The repo buttons(Watch, Star, Fork) on mobile were showing quite big and the SVG wasn't even displayed on the same line, if the count of those numbers were too high it would even overflow. This commit removes the SVG, as there isn't any place to show them on the same row and allows them to have a new row if the counts of those buttons are high. - The admin page can show you a lot of interesting information, on mobile the System Status + Configuration weren't properly displayed as the margin's were too high. This commit fixes that by reducing the margin to a number that makes sense on mobile. - Fixes to not overflow the tables but instead force them to be scrollable. - When viewing a issue or pull request, the comments aren't full-width but instead 80% and aligned to right, on mobile this is a annoyance as there isn't much width to begin with. This commits fixes that by forcing full-width and removing the avatars on the left side and instead including them inline in the comment header. Gusted authored at GitHub comitted at
  13. ac6c3384 Add API to check if team has repo access (#19540) * Add API to check if team has repo access * Add test case qwerty287 authored at GitHub comitted at
  14. edff571a Avoid MoreThanOne Error (#19557) 99rgosse authored at GitHub comitted at
  15. 094c8fdc [skip ci] Updated licenses and gitignores GiteaBot authored at GiteaBot comitted at
  16. c0a6309a Simplify loops to copy (#19569) - Simplify two loops into `copy` statements. Gusted authored at GitHub comitted at
  17. 1597e2da Use middleware to open gitRepo (#19559) 6543 authored at GitHub comitted at
  18. d23f2203 Added X-Mailer header to outgoing emails (#19562) - It's a non-standard mentioned in https://www.ietf.org/rfc/rfc2076.html#section-3.4 - This header makes emails filtering easier Ivan Fedorov authored at GitHub comitted at
  19. 8d34c2fa fix #19545 (#19563) 6543 authored at GitHub comitted at
  20. bf7258be [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  21. 5aebc4f0 Respect DefaultUserIsRestricted system default when creating new user (#19310) * Apply DefaultUserIsRestricted in CreateUser * Enforce system defaults in CreateUser Allow for overwrites with CreateUserOverwriteOptions * Fix compilation errors * Add "restricted" option to create user command * Add "restricted" option to create user admin api * Respect default setting.Service.RegisterEmailConfirm and setting.Service.RegisterManualConfirm where needed * Revert "Respect default setting.Service.RegisterEmailConfirm and setting.Service.RegisterManualConfirm where needed" This reverts commit ee95d3e8dc9e9fff4fa66a5111e4d3930280e033. Jimmy Praet authored at GitHub comitted at
  22. 219c87e7 Mute link in diff header (#19556) Followup to https://github.com/go-gitea/gitea/pull/19534. Make the link render in color only on hover. silverwind authored at GitHub comitted at
  23. ad6d08d1 Add API to query collaborators permission for a repository (#18761) Targeting #14936, #15332 Adds a collaborator permissions API endpoint according to GitHub API: https://docs.github.com/en/rest/collaborators/collaborators#get-repository-permissions-for-a-user to retrieve a collaborators permissions for a specific repository. ### Checks the repository permissions of a collaborator. `GET` `/repos/{owner}/{repo}/collaborators/{collaborator}/permission` Possible `permission` values are `admin`, `write`, `read`, `owner`, `none`. ```json { "permission": "admin", "role_name": "admin", "user": {} } ``` Where `permission` and `role_name` hold the same `permission` value and `user` is filled with the user API object. Only admins are allowed to use this API endpoint. Florin Hillebrand authored at GitHub comitted at
  24. e5c6c001 Permalink files In PR diff (#19534) KN4CK3R authored at GitHub comitted at
  25. 3e2bba08 Fix Pull Request comment filename word breaks (#19535) * Fix word breaks in Chrome This fixes word wrapping on the filename for a comment on a PR. A previous commit fixed this problem in Firefox, but not Chrome. Fixes #16248 * Don't break Outdated badge This prevents the Outdated badge on a PR from wrapping in the middle of the word for a comment on a long filename. * Move word break to recommended element * Add overflow-wrap per PR review * Update web_src/less/helpers.less Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> parnic authored at GitHub comitted at
  26. 334707fe Don't error when branch's commit doesn't exist (#19547) * Don't error when branch's commit doesn't exist - If one of the branches no longer exists, don't throw an error, it's possible that the branch was destroyed during the process. Simply skip it and disregard it. - Resolves #19541 * Don't send empty objects * Use more minimal approach Gusted authored at GitHub comitted at
  27. 53829b84 [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  28. a51efb4c Support `hostname:port` to pass host matcher's check #19543 (#19543) hostmatcher: split the hostname from the `hostname:port` string, use the correct hostname to do the match. wxiaoguang authored at GitHub comitted at
  29. 8eb1cd92 Add "Allow edits from maintainer" feature (#18002) Adds a feature [like GitHub has](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) (step 7). If you create a new PR from a forked repo, you can select (and change later, but only if you are the PR creator/poster) the "Allow edits from maintainers" option. Then users with write access to the base branch get more permissions on this branch: * use the update pull request button * push directly from the command line (`git push`) * edit/delete/upload files via web UI * use related API endpoints You can't merge PRs to this branch with this enabled, you'll need "full" code write permissions. This feature has a pretty big impact on the permission system. I might forgot changing some things or didn't find security vulnerabilities. In this case, please leave a review or comment on this PR. Closes #17728 Co-authored-by: 6543 <6543@obermui.de> qwerty287 authored at GitHub comitted at
  30. 92dfbada Better describe what `/repos/{owner}/{repo}/raw/{filepath}` returns on 200 (#19542) - Set on the description that it returns the raw file content. - Resolves #19514 Gusted authored at GitHub comitted at