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
..
actions.go
admin.go
api.go
attachment.go
cache.go
camo.go
config_provider.go
cors.go
cron.go
cron_test.go
database.go
database_sqlite.go
database_test.go
federation.go
git.go
highlight.go
i18n.go
incoming_email.go
indexer.go
indexer_test.go
lfs.go
log.go
mailer.go
mailer_test.go
markup.go
metrics.go
migrations.go
mime_type_map.go
mirror.go
oauth2.go
other.go
packages.go
packages_test.go
picture.go
project.go
proxy.go
queue.go
repository.go
security.go
server.go
service.go
session.go
setting.go
setting_test.go
ssh.go
storage.go
storage_test.go
task.go
time.go
ui.go	Add ONLY_SHOW_RELEVANT_REPOS back, fix explore page bug, make code more strict (#23766)	2023-03-29 08:41:45 -05:00
webhook.go