1. Top
  2. gitea
  3. Commits
gitea

Development moved to Codeberg

Commits at dd1ed35f756ea1087f0c55618d6cf745192b612d

  1. dd1ed35f Add dbconsistency checks for Stopwatches (#20010) It appears possible that stopwatches can become orphaned or have been orphaned in the past. This PR adds Orphan checks for Stopwatches. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> zeripath authored at GitHub comitted at
  2. fd0d481d fix push mirrors URL are no longer displayed on the UI (#20011) * fix push mirrors URL are no longer displayed on the UI Signed-off-by: Mohamed Sekour <mohamed.sekour@exfo.com> * Update modules/templates/helper.go Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Mohamed Sekour authored at GitHub comitted at
  3. 8eefe2af Empty log queue on flush and close (#19994) * Empty log queue on flush and close It is possible for log events to remain in the buffer off the multichannelledlog and thus not be logged despite close or flush. This PR simply adds a function to empty the queue before closing or flushing. (Except when the logger is paused.) Reference #19982 Signed-off-by: Andrew Thornton <art27@cantab.net> * and do similar for ChannelledLog Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> zeripath authored at GitHub comitted at
  4. 46e50bcb [skip ci] Updated translations via Crowdin zeripath authored at zeripath comitted at
  5. ae446b13 Stop spurious APIFormat stopwatches logs (#20008) If there are dangling stopwatches with missing issues there will be repeated logging of Unable to APIFormat stopwatches. These are unhelpful and instead we should only log if the error is not an issue not exist error. And we should also prevent an error on missing issue in GetActiveStopwatch too Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  6. 5d80feb5 Fix CountOrphanedLabels in orphan check (#20009) gitea doctor --run check-db-consistency is currently broken due to an incorrect and old use of Count() with a string. Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  7. 1e9ad8eb Write Commit-Graphs in RepositoryDumper (#20004) When migrating git repositories we should ensure that the commit-graph is written. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: delvh <dev.lh@web.de> zeripath authored at GitHub comitted at
  8. ea9997a9 Add fetch.writeCommitGraph to gitconfig (#20006) Add fetch.writeCommitGraph to gitconfig to ensure that a commit-graph will be written on git fetch calls. Signed-off-by: Andrew Thornton <art27@cantab.net> zeripath authored at GitHub comitted at
  9. 27ba86d2 move agit dependcy (#19998) Lunny Xiao authored at GitHub comitted at
  10. 719eb4a8 Fix a JS error in initRepoCommitLastCommitLoader's entryMap (#19996) wxiaoguang authored at GitHub comitted at
  11. a0365072 gitconfig: set safe.directory = * (#19870) Allow git push to work when networked file systems with mixed ownership are used with Gitea docker images >= 1.16.6 or Gitea binaries running alongside git versions published after 04/2022. There are circumstances independent of Gitea (networked file systems with various permission systems) by which the git repositories managed by Gitea may have mixed owners. It is not a behavior that Gitea have control over nor is it a problem as long as the permissions for Gitea to operate are correct. Gitea instances have been operating under these conditions for a number of years. It is detected as a potential security risk ( see GHSA-vw2c-22j4-2fh2 ) by the most recent git versions. However, Gitea always runs git commands with a current directory matching the repository on which it operates. That makes Gitea immune from this security problem and it is safe to ignore the mixed owner permission check. This gitconfig modification is done on a file dedicated to the user exclusively used by Gitea. Fixes: #19455 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: zeripath <art27@cantab.net> singuliere authored at GitHub comitted at
  12. bdde56c9 Fix Readme render bug (#19992) Fix #19988 Co-authored-by: zeripath <art27@cantab.net> Lunny Xiao authored at GitHub comitted at
  13. 1e05adfc Delete duplicated update btn on pull request view page (#19993) Fix #19987 Lunny Xiao authored at GitHub comitted at
  14. 9068c784 Use DisplayName() instead of FullName in Oauth provider (#19991) Use DisplayName() in Oauth as this provides a fallback if FullName is not set. Closes #19382 oGi4i authored at GitHub comitted at
  15. e3e06d13 fix permission check for delete tag (#19985) fix #19970 by the way, fix some error response about protected tags. Signed-off-by: a1012112796 <1012112796@qq.com> a1012112796 authored at GitHub comitted at
  16. 89b0aac3 [skip ci] Updated translations via Crowdin wxiaoguang authored at wxiaoguang comitted at
  17. 157b4057 Remove legacy git code (ver < 2.0), fine tune markup tests (#19930) * clean git support for ver < 2.0 * fine tune tests for markup (which requires git module) * remove unnecessary comments * try to fix tests * try test again * use const for GitVersionRequired instead of var * try to fix integration test * Refactor CheckAttributeReader to make a *git.Repository version * update document for commit signing with Gitea's internal gitconfig * update document for commit signing with Gitea's internal gitconfig Co-authored-by: Andrew Thornton <art27@cantab.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> wxiaoguang authored at GitHub comitted at
  18. 70ce051f [skip ci] Updated translations via Crowdin Gusted authored at Gusted comitted at
  19. 36127a33 Don't prevent overflow on y-as (#19978) - Fomantic tries to prevent overflowing on the `y/x`-as by default on stackable menu's on mobile screens. We already solve this issue by forcing overflow on x as and hide it on y as(due to some issues with other menu's), since https://github.com/go-gitea/gitea/pull/19486. - However this edge case does require a y-overflow to show the dropdown, because you cannot easily adjust this with CSS, once you're fiddling with overflow's (https://stackoverflow.com/a/6433475). However interesting behavior is noted https://css-tricks.com/popping-hidden-overflow/ when you remove the position: relative, it will suddenly work again. Well because this is the only solution without redesigning dropdowns, I think we can live with the side-effect of the dropdown items being full-width instead "relative" width to their parent. - Resolves #19976 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Gusted authored at GitHub comitted at
  20. d05fb6f6 [skip ci] Updated translations via Crowdin a1012112796 authored at a1012112796 comitted at
  21. a6b7c364 fix `go to file` link for mirror repository (#19983) the `BaseRepo` not always exit, should use `Repository`. Signed-off-by: a1012112796 <1012112796@qq.com> a1012112796 authored at GitHub comitted at
  22. e399f0f5 Don't buffer doctor logger (#19982) - We don't need to buffer the logger with a thousand capacity. It's not a high-throughput logger, this also caused issue whereby the logger can't keep up with repeated messages being send(somehow they are lost in the queue?). - Resolves #19969 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Gusted authored at GitHub comitted at
  23. b01dce2a Allow render HTML with css/js external links (#19017) * Allow render HTML with css/js external links * Fix bug because of filename escape chars * Fix lint * Update docs about new configuration item * Fix bug of render HTML in sub directory * Add CSP head for displaying iframe in rendering file * Fix test * Apply suggestions from code review Co-authored-by: delvh <dev.lh@web.de> * Some improvements * some improvement * revert change in SanitizerDisabled of external renderer * Add sandbox for iframe and support allow-scripts and allow-same-origin * refactor * fix * fix lint * fine tune * use single option RENDER_CONTENT_MODE, use sandbox=allow-scripts * fine tune CSP * Apply suggestions from code review Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: delvh <dev.lh@web.de> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Lunny Xiao authored at GitHub comitted at
  24. 7d1770cd Use correct count for `NumOpenIssues` (#19980) - Don't specify the field in `Count` instead use `Cols` for this. - Call `log.Error` when a error occur. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Gusted authored at GitHub comitted at
  25. 6473bd33 In code search, get code unit accessible repos in one (main) query (#19764) * When non-admin users use code search, get code unit accessible repos in one main query * Modified some comments to match the changes * Removed unnecessary check for Access Mode in Collaboration table Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Lauris BH <lauris@nix.lv> Hugo Hoitink authored at GitHub comitted at
  26. 88164652 [skip ci] Updated translations via Crowdin Gusted authored at Gusted comitted at
  27. f0ce5470 Always try to fetch repo for mirrors (#19975) - Always give a best-effort to fetching the repositories, if even that fails indeed give a disconnected mirror found error. - *Partially* resolves #19928 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Gusted authored at GitHub comitted at
  28. 1f8f9c38 Remove tab/TabName usage where it's not needed (#19973) `tab` query argument and `TabName` in context is used only in profile so remove it from all other places where it's not used anymore. Lauris BH authored at GitHub comitted at
  29. 9f87b60b Fix cli command restore-repo: "units" should be parsed as StringSlice (#19953) * Fix cli command restore-repo: "units" should be parsed as StringSlice because after #15790 it's read by c.StringSlice("units"). Before, the "units" were processed by strings.Split * Add checking for invalid unit names Co-authored-by: 6543 <6543@obermui.de> wxiaoguang authored at GitHub comitted at
  30. 97548d27 Uppercase first languages letters (#19965) AHOHNMYC authored at GitHub comitted at