forgejo/docs/content/doc/administration
wxiaoguang e57e1144c5
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.
2023-03-29 08:41:45 -05:00
..
adding-legal-pages.en-us.md
backup-and-restore.en-us.md
backup-and-restore.zh-cn.md
backup-and-restore.zh-tw.md
cmd-embedded.en-us.md
command-line.en-us.md
config-cheat-sheet.en-us.md Add ONLY_SHOW_RELEVANT_REPOS back, fix explore page bug, make code more strict (#23766) 2023-03-29 08:41:45 -05:00
config-cheat-sheet.zh-cn.md
customizing-gitea.en-us.md
customizing-gitea.zh-cn.md
email-setup.en-us.md
environment-variables.en-us.md
environment-variables.zh-cn.md
external-renderers.en-us.md
fail2ban-setup.en-us.md
fail2ban-setup.zh-cn.md
git-lfs-support.en-us.md
https-support.en-us.md
logging-documentation.en-us.md
mail-templates.en-us.md
repo-indexer.en-us.md
reverse-proxies.en-us.md
reverse-proxies.zh-cn.md
search-engines-indexation.en-us.md
signing.en-us.md