1. Top
  2. gitea
  3. Commits
gitea

Development moved to Codeberg

Commits at 7b25a010c89835e036f1b0cc5af65249bfd2781b

  1. 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
  2. 8422b1c5 [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  3. 99d14f60 Add separate SSH_USER config option (#17584) Co-authored-by: zeripath <art27@cantab.net> Clar Fon authored at GitHub comitted at
  4. 9911b66a Be more lenient with label colors (#17752) Accept 12-bit color specifications. Clar Fon authored at GitHub comitted at
  5. 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
  6. 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
  7. 47c1b623 No longer show the db-downgrade SQL in production (#18653) * make messages more friendly wxiaoguang authored at GitHub comitted at
  8. c2a3e381 Fix the missing i18n key for update checker (#18646) wxiaoguang authored at GitHub comitted at
  9. 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
  10. 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
  11. 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
  12. 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
  13. 3043eb36 Delete old git.NewCommand() and use it as git.NewCommandContext() (#18552) 6543 authored at GitHub comitted at
  14. 8ae5e6d7 Update JS dependencies (#18636) silverwind authored at GitHub comitted at
  15. da41820a fix commits_list_small.tmpl (#18641) Signed-off-by: a1012112796 <1012112796@qq.com> a1012112796 authored at GitHub comitted at
  16. 37ead26e Fix `make fmt` and `make fmt-check` (#18633) * Run 'make fmt' 'make fmt' currently produces this change, I'm not sure how CI did not fail on it, I made sure I have `mvdan.cc/gofumpt@latest`. * Fix 'make fmt-check' `make fmt-check` did not run all commands that `make fmt` did, resulting in missed diffs. Fix that by just depending on the `fmt` target. Includes: https://github.com/go-gitea/gitea/pull/18633 * Make gitea-fmt work with -l and -d and integrate gofumpt This implements -l, -w and -d with gitea-fmt and merges gofumpt. Signed-off-by: Andrew Thornton <art27@cantab.net> * as per silverwind Signed-off-by: Andrew Thornton <art27@cantab.net> * Apply suggestions from code review * use -l instead of -d for fmt-check Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: Andrew Thornton <art27@cantab.net> silverwind authored at GitHub comitted at
  17. 7b6c1f80 Frontport of changelog for v1.16.1 (#18615) * Add changelog for v1.16.1 * Update 1.16.1 Lunny Xiao authored at GitHub comitted at
  18. 7a42e357 Pass correct context (#18638) - Pass the correct context into `db.GetEngine()`. - Introduced in: https://github.com/go-gitea/gitea/pull/18604 Gusted authored at GitHub comitted at
  19. ce8eb20a comments on migrated issues/prs must link to the comment ID (#18630) Instead of the issue ID which is not a valid anchor. Signed-off-by: singuliere <singuliere@autistici.org> singuliere authored at GitHub comitted at
  20. 8bd89ca2 preserve users if restoring a repository on the same Gitea instance (#18604) When calling DumpRepository and RestoreRepository on the same Gitea instance, the users are preserved: all labels, issues etc. belong to the external user who is, in this particular case, the local user. Dead code verifying g.gitServiceType.Name() == "" (i.e. plain git) is removed. The function is never called because the plain git downloader does not migrate anything that is associated to a user, by definition. Errors returned by GetUserIDByExternalUserID are no longer ignored. The userMap is used when the external user is not kown, which is the most common case. It was only used when the external user exists which happens less often and, as a result, every occurence of an unknown external user required a SQL query. 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
  21. 9419dd2b Stop logging an error when notes are not found (#18626) This is an unnecessary logging event. Fix #18616 Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  22. 3b33507c [skip ci] Updated licenses and gitignores GiteaBot authored at GiteaBot comitted at
  23. 7ba1b711 Only attempt to flush queue if the underlying worker pool is not finished (#18593) * Only attempt to flush queue if the underlying worker pool is not finished There is a possible race whereby a worker pool could be cancelled but yet the underlying queue is not empty. This will lead to flush-all cycling because it cannot empty the pool. Signed-off-by: Andrew Thornton <art27@cantab.net> * Apply suggestions from code review Co-authored-by: Gusted <williamzijl7@hotmail.com> Co-authored-by: Gusted <williamzijl7@hotmail.com> zeripath authored at GitHub comitted at
  24. a51d2114 quote MAKE to prevent path expansion with space error (#18622) Pretty minor change to prevent error when `$(MAKE)` path is expanded with a space in the path. ```bash $ TAGS="bindata sqlite sqlite_unlock_notify" make build /usr/bin/sh: -c: line 0: syntax error near unexpected token `(' /usr/bin/sh: -c: line 0: `C:/Program Files (x86)/GnuWin32/bin/make -v | head -n 1' ``` I believe Program Files (x86) is the default path for GNU make on windows Kyle D authored at GitHub comitted at
  25. 933e8191 Ensure that blob-excerpt links work for wiki (#18587) It appears that the blob-excerpt links do not work on the wiki - likely since their introduction. This PR adds support for the wiki on these links. Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  26. aa23f477 Use `CryptoRandomBytes` instead of `CryptoRandomString` (#18439) - Switch to use `CryptoRandomBytes` instead of `CryptoRandomString`, OAuth's secrets are copied pasted and don't need to avoid dubious characters etc. - `CryptoRandomBytes` gives ![2^256 = 1.15 * 10^77](https://render.githubusercontent.com/render/math?math=2^256%20=%201.15%20\cdot%2010^77) `CryptoRandomString` gives ![62^44 = 7.33 * 10^78](https://render.githubusercontent.com/render/math?math=62^44%20=%207.33%20\cdot%2010^78) possible states. - Add a prefix, such that code scanners can easily grep these in source code. - 32 Bytes + prefix Gusted authored at GitHub comitted at
  27. 88939a56 Remove the spurious space in the .ui.right additional selector (#18605) Somehow a spurious space sneaked in to #18538 this PR simply removes it. Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  28. 3c737410 Ensure commit-statuses box is sized correctly in headers (#18538) * Ensure commit-statuses box is sized correctly in headers When viewing commits as commits the commit-status box will be fixed at 30px in height due to being forced to be this size by a fomantic selector. This PR simply adds a few more selectors to force this to have height auto. Fix #18498 Signed-off-by: Andrew Thornton <art27@cantab.net> * Update web_src/less/_repository.less Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> zeripath authored at GitHub comitted at
  29. 319d191a [skip ci] Updated translations via Crowdin GiteaBot authored at GiteaBot comitted at
  30. 1ab44cb0 Prevent merge messages from being sorted to the top of email chains (#18566) * Prevent merge messages from being sorted to the top of email chains Gitea will currrently resend the same message-id for the closed/merged/reopened messages for issues. This will cause the merged message to leap to the top of an email chain and become out of sync. This PR adds specific suffices for these actions. Fix #18560 Signed-off-by: Andrew Thornton <art27@cantab.net> * add test Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at