diff options
| author | wxiaoguang <wxiaoguang@gmail.com> | 2023-03-29 21:41:45 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-29 08:41:45 -0500 |
| commit | e57e1144c5ae7a2995e6818c6ae32139e563add7 (patch) | |
| tree | eea2b49bef9f1469f99467b5855f74fc28274db4 /custom/conf | |
| parent | ed5e7d03c6c44666c6fe97a15e8ce33d223c4466 (diff) | |
| download | gitea-e57e1144c5ae7a2995e6818c6ae32139e563add7.tar.gz gitea-e57e1144c5ae7a2995e6818c6ae32139e563add7.zip | |
Add ONLY_SHOW_RELEVANT_REPOS back, fix explore page bug, make code more strict (#23766)
Follow #21962
After I eat my own dogfood, I would say that
ONLY_SHOW_RELEVANT_REPOS=false is necessary for many private/enterprise
instances, because many private repositories do not have
"description/topic", users just want to search by their names.
This PR also adds `PageIsExploreRepositories` check, to make code more
strict, because the `search` template is shared for different purpose.
And during the test, I found a bug that the "Search" button didn't
respect the "relevant" parameter, so this PR fixes the bug by the way
together.
I think this PR needs to be backported.
Diffstat (limited to 'custom/conf')
| -rw-r--r-- | custom/conf/app.example.ini | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/custom/conf/app.example.ini b/custom/conf/app.example.ini index 5e0d16b042..2a840d5ef1 100644 --- a/custom/conf/app.example.ini +++ b/custom/conf/app.example.ini @@ -1238,6 +1238,10 @@ ROUTER = console ;; ;; Whether to enable a Service Worker to cache frontend assets ;USE_SERVICE_WORKER = false +;; +;; Whether to only show relevant repos on the explore page when no keyword is specified and default sorting is used. +;; A repo is considered irrelevant if it's a fork or if it has no metadata (no description, no icon, no topic). +;ONLY_SHOW_RELEVANT_REPOS = false ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; |