1. Top
  2. gitea
  3. Commits
gitea

Development moved to Codeberg

Commits at 581d29ec1dc7289415d5fd8361aa9a5221ba7ad2

  1. 581d29ec Update SSH Server crypto settings (#18697) - Use a better and more curated list of Ciphers and KeyExchanges, these roughly follows OpenSSH's default. - Remove some cryptography values which were deprecated. Gusted authored at GitHub comitted at
  2. 0c70b4c2 Fix bug for version update hint (#18701) Co-authored-by: silverwind <me@silverwind.io> Lunny Xiao authored at GitHub comitted at
  3. 7489d96d Fix issue with docker-rootless shimming script (#18690) zeripath authored at GitHub comitted at
  4. bc8e19ec tests: remove redundant comparison in repo dump/restore (#18660) It is a leftover forgotten in https://github.com/go-gitea/gitea/pull/18621 Signed-off-by: singuliere <singuliere@autistici.org> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> singuliere authored at GitHub comitted at
  5. e034d3a7 [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  6. c917f2df Disable unnecessary OpenID/OAuth2 elements (#18491) This mod fixes disabling unnecessary OpenID elements. Related: https://github.com/go-gitea/gitea/pull/13129 Author-Change-Id: IB#1115256 Paweł Bogusławski authored at GitHub comitted at
  7. eb748f5f Add apply-patch, basic revert and cherry-pick functionality (#17902) This code adds a simple endpoint to apply patches to repositories and branches on gitea. This is then used along with the conflicting checking code in #18004 to provide a basic implementation of cherry-pick revert. Now because the buttons necessary for cherry-pick and revert have required us to create a dropdown next to the Browse Source button I've also implemented Create Branch and Create Tag operations. Fix #3880 Fix #17986 Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  8. 439ad34c C preprocessor colors improvement (#18671) * C preprocessor colors improvement Fixes #18670 * Update web_src/less/chroma/light.less Co-authored-by: KN4CK3R <admin@oldschoolhack.me> * typo missing semi * add color for #include filenames Co-authored-by: KN4CK3R <admin@oldschoolhack.me> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Bruno Raoult authored at GitHub comitted at
  9. 55793455 Update object repo with the migrated repository (#18684) When migrating a repository (from GitHub) using the API (**POST** `repos/migrate`), the Code Indexer is not updated. Searching in the user interface will not return any results. When migrating the same repository using **+/New Migration** in the web interface, the search index is updated and searching works as expected. Caused by the fact that object `repo` is never updated with the migrated repo so `setting.Indexer.RepoIndexerEnabled && !repo.IsEmpty` in `modules/notification/indexer/indexer.go:NotifyMigrateRepository` always evaluates to `false`. Tested with gitea:1.16.1, MariaDB:10, Breve in `Run Mode: Dev`. Hugo Hoitink authored at GitHub comitted at
  10. 2f766082 Prevent security failure due to bad APP_ID (#18678) WebAuthn may cause a security exception if the provided APP_ID is not allowed for the current origin. Therefore we should reattempt authentication without the appid extension. Also we should allow [u2f] as-well as [U2F] sections. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> zeripath authored at GitHub comitted at
  11. 4160aff8 [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  12. ae0d8d94 Let `MinUnitAccessMode` return correct perm (#18675) - Don't let `TypeExternalTracker` or `TypeExternalWiki` influence the minimal permission, as they won't be higher than read. So even if all the other ones are write, these 2 will ensure that's not higher than read. - Partially resolves #18572 (Point 1,2,5?) Co-authored-by: zeripath <art27@cantab.net> Gusted authored at GitHub comitted at
  13. f8b21ac0 Simplify Boost/Pause logic (#18673) * Simplify Boost/Pause logic #18658 has added a check to see if we need to boost because there is still work to do however the check is slightly complex and not ideal. There's no point boosting if the queue is paused or can't scale. Therefore merge the two selects into one and add a check to p.paused. Signed-off-by: Andrew Thornton <art27@cantab.net> * And on resume add a zeroboost if necessary Signed-off-by: Andrew Thornton <art27@cantab.net> * simplify Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lauris BH <lauris@nix.lv> zeripath authored at GitHub comitted at
  14. c14ca34d update the comparison documents (#18669) * update the comparison documents * Remove U2f Lunny Xiao authored at GitHub comitted at
  15. df440173 Restart zero worker if there is still work to do (#18658) * Restart zero worker if there is still work to do It is possible for the zero worker to timeout before all the work is finished. This may mean that work may take a long time to complete because a worker will only be induced on repushing. Also ensure that requested count is reset after pulls and push mirror sync requests and add some more trace logging to the queue push. Fix #18607 Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  16. 4d939845 Added auto-save whitespace behavior if it changed manually (#15566) Viktor Suprun authored at GitHub comitted at
  17. 60f20338 Support custom ACME provider (#18340) * Added ACMECAURL option to support custom ACME provider. Closes #18306 * Refactor setting.go https settings, renamed options and variables, and documented app.example.ini * Refactored runLetsEncrypt to runACME * Improved documentation Cristian Le authored at GitHub comitted at
  18. a60e8be8 Refactor i18n, use Locale to provide i18n/translation related functions (#18648) * remove unnecessary web context data fields, and unify the i18n/translation related functions to `Locale` * in development, show an error if a translation key is missing * remove the unnecessary loops `for _, lang := range translation.AllLangs()` for every request, which improves the performance slightly * use `ctx.Locale.Language()` instead of `ctx.Data["Lang"].(string)` * add more comments about how the Locale/LangType fields are used wxiaoguang authored at GitHub comitted at
  19. 7b25a010 Only request write when necessary (#18657) * Only request write when necessary - Only request write for `INTERNAL_TOKEN_URI` when no token was found. - Resolves #18655 * Fix perm * Update setting.go * Update setting.go * Update setting.go Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: zeripath <art27@cantab.net> Gusted authored at GitHub comitted at
  20. 8422b1c5 [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  21. 99d14f60 Add separate SSH_USER config option (#17584) Co-authored-by: zeripath <art27@cantab.net> Clar Fon authored at GitHub comitted at
  22. 9911b66a Be more lenient with label colors (#17752) Accept 12-bit color specifications. Clar Fon authored at GitHub comitted at
  23. 3a91f845 remove redundant call to UpdateRepoStats during migration (#18591) There is no need to call UpdateRepoStats in the InsertIssues and InsertPullRequests function. They are only called during migration by the CreateIssues and CreateReviews methods of the gitea uploader. The UpdateRepoStats function will be called by the Finish method of the gitea uploader after all reviews and issues are inserted. Calling it before is therefore redundant and the associated SQL requests are not cheap. The statistics tests done after inserting an issue or a pull request are also removed. They predate the implementation of UpdateRepoStats, back when the calculation of the statistics was an integral part of the migration function. The UpdateRepoStats is now tested independantly and these tests are no longer necessary. Signed-off-by: singuliere <singuliere@autistici.org> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> singuliere authored at GitHub comitted at
  24. 5faf0550 more repo dump/restore tests, including pull requests (#18621) The tests were refactored so that all YAML files content are checked, unless an exception is set (for instance for the Updated field which is automatically updated by the database and cannot be expected to be identical over a dump/restore/dump round. This approach helps catch more errors where fields are added in the migration files because they do not need to be added to the tests to be verified. It also helps as a reminder of what is left to be implemented, such as the the Assignees field in issues. A helper is added to keep the tests DRY and facilitate their maintenance. Signed-off-by: Loïc Dachary <loic@dachary.org> Co-authored-by: Loïc Dachary <loic@dachary.org> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> singuliere authored at GitHub comitted at
  25. 47c1b623 No longer show the db-downgrade SQL in production (#18653) * make messages more friendly wxiaoguang authored at GitHub comitted at
  26. c2a3e381 Fix the missing i18n key for update checker (#18646) wxiaoguang authored at GitHub comitted at
  27. f393bc82 Update gitea-vet (#18640) * Update gitea-vet - Update gitea-vet to include latest 2 changes https://gitea.com/gitea/gitea-vet/compare/7c98703580bef612b10f6a603883052f79acf9c0...master * Tidy up go.sum Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: zeripath <art27@cantab.net> Gusted authored at GitHub comitted at
  28. 9712f7d6 Future proof for 1.18 (#18644) - Update json-iterator/go to handle 1.18's new memory model with slices. - Don't panic while running gitea with go 1.18 Gusted authored at GitHub comitted at
  29. 6ada0594 Add `contrib/upgrade.sh` (#18286) Adds an upgrade script that automates upgrading installations on Linux from binary releases, so people don't need to reinvent the wheel. Hopefully this leads to less questions about how to upgrade, and consequently less Gitea instances running unmaintained versions in the wild. Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: 6543 <6543@obermui.de> Norwin authored at GitHub comitted at
  30. a6e657e9 If rendering has failed due to a net.OpError stop rendering (#18642) When a net.OpError occurs during rendering the underlying connection is essentially dead and therefore attempting to render further data will only cause further errors. Therefore in serverErrorInternal detect if the passed in error is an OpError and if so do not attempt any further rendering. Fix #18629 Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at