Global Repo search #5773

New Issue

GiteaMirror · 2025-11-02T06:35:28-06:00

GiteaMirror commented

2025-11-02 06:35:28 -06:00

Originally created by @bryanpedini on GitHub (Jul 23, 2020).

Gitea version (or commit ref): 1.12.2
Git version: 2.18.4
Operating system: CentOS 8 LXC Container on ProxMox VE 6 (does it matter?)
Database (use [x]): MySQL
Can you reproduce the bug at https://try.gitea.io: Yes (just find a repo that doesn't 500 the server and look)
Log gist: N/A

Description

I don't know if this has been already reported, one of the things I would like to be addressed on Gitea is a better search engine, because after one page of results I didn't find this issue on GitHub, so feel free to just close it if it's already been addressed.

I would really like to see a "global / in-repo" search option in Gitea like here on GitHub; I know it would require massive work and effort, as well as a lot of computational resources for the hosting server with this feature enabled, when there is a lot of code involved; but I think it would be a nice addition... (perhaps low-priority 1.x.x milestone?)

Screenshots

Modified HTML code to include a search bar, kinda what it could be like:

Code:

<input class="item" type="text" name="search-bar" placeholder="Search..." style="border: 2px solid #bbbbbb; border-radius: 15px; padding-left: 15vw; min-width: 35vw;">

Originally created by @bryanpedini on GitHub (Jul 23, 2020). - Gitea version (or commit ref): 1.12.2 - Git version: 2.18.4 - Operating system: CentOS 8 LXC Container on ProxMox VE 6 (does it matter?) - Database (use `[x]`): MySQL - Can you reproduce the bug at https://try.gitea.io: Yes (just find a repo that doesn't 500 the server and look) - Log gist: N/A ## Description I don't know if this has been already reported, one of the things I would like to be addressed on Gitea is a better search engine, because after one page of results I didn't find this issue on GitHub, so feel free to just close it if it's already been addressed. I would really like to see a "global / in-repo" search option in Gitea like here on GitHub; I know it would require massive work and effort, as well as a lot of computational resources for the hosting server with this feature enabled, when there is a lot of code involved; but I think it would be a nice addition... (perhaps low-priority 1.x.x milestone?) ## Screenshots Modified HTML code to include a search bar, kinda what it _could_ be like: ![Screenshot from 2020-07-23 18-40-33](https://user-images.githubusercontent.com/45012292/88313644-1d218f00-cd14-11ea-84cf-5f8ba8e43326.png) Code: ``` <input class="item" type="text" name="search-bar" placeholder="Search..." style="border: 2px solid #bbbbbb; border-radius: 15px; padding-left: 15vw; min-width: 35vw;"> ```

GiteaMirror added the type/feature label 2025-11-02 06:35:28 -06:00

GiteaMirror commented

2025-11-02 06:35:28 -06:00

@jolheiser commented on GitHub (Jul 23, 2020):

Is this issue about the lack of the search bar on the main navbar, or a search itself?

Gitea already has code searching/indexing which is disabled by default because of disk usage.
This is disabled on try, for example, because of excessive disk usage on a public demo.

REPO_INDEXER_ENABLED
https://docs.gitea.io/en-us/config-cheat-sheet/#indexer-indexer

@jolheiser commented on GitHub (Jul 23, 2020): Is this issue about the lack of the search bar on the main navbar, or a search itself? Gitea already has code searching/indexing which is disabled by default because of disk usage. This is disabled on try, for example, because of excessive disk usage on a public demo. `REPO_INDEXER_ENABLED` https://docs.gitea.io/en-us/config-cheat-sheet/#indexer-indexer

GiteaMirror commented

2025-11-02 06:35:29 -06:00

@bryanpedini commented on GitHub (Jul 24, 2020):

Is this issue about the lack of the search bar on the main navbar, or a search itself?

More a feature proposal issue about a "global search" like here on GitHub. (sorry, I didn't explain myself enough before)
It happens more then I myself thought it would, that I need to find a file that contained that specific piece of code, and have it on GitHub makes lifes a lot easier.

As stated before, I know it can be both time consuming and hard to implement, and resource heavy on the computational power; however, I think it would benefit even (if not mostly) the small developers that host their own code in their private Gitea instance, to be able to search one single term and find all the issues, all the pull requests, and all the instances that search term appears in the code, all in one function bar at the top of the website / repository; with, maybe, like here on GH, the ability to decide to slowly wait for a search on the entire server (all tho much restricted, only on repo name, description and tags for example), or in the currently-browsing repository only (with also in-depth code search, issues, wiki, PRs and releases perhaps).

@bryanpedini commented on GitHub (Jul 24, 2020): > Is this issue about the lack of the search bar on the main navbar, or a search itself? More a feature proposal issue about a "global search" like here on GitHub. (sorry, I didn't explain myself enough before) It happens more then I myself thought it would, that I need to find a file that contained that specific piece of code, and have it on GitHub makes lifes a lot easier. As stated before, I know it can be both time consuming and hard to implement, and resource heavy on the computational power; however, I think it would benefit even (if not mostly) the small developers that host their own code in their private Gitea instance, to be able to search one single term and find all the issues, all the pull requests, and all the instances that search term appears in the code, all in one function bar at the top of the website / repository; with, maybe, like here on GH, the ability to decide to slowly wait for a search on the entire server (all tho much restricted, only on repo name, description and tags for example), or in the currently-browsing repository only (with also in-depth code search, issues, wiki, PRs and releases perhaps).

GiteaMirror commented

2025-11-02 06:35:29 -06:00

@stale[bot] commented on GitHub (Oct 12, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 12, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:35:29 -06:00

@camlafit commented on GitHub (Jul 1, 2021):

Hello

Could be nice to provide a global search.
If we following github behavior, we can do a search on :

repository name
code
commits
issues
wiki
users

And some more (but doesn't looks) related to gitea features.
https://github.com/search?q=gitea

We can filter in a specific organization or repository.

In gitlab we can obtain result on :

Projects
Issues
Merge requests
Milestones
Users

https://gitlab.com/search?group_id=&nav_source=navbar&project_id=&repository_ref=&search=gitea&snippets=false

If I've understood gitea indexer behavior we can do search on commit and code and search feature is only displayed on commits page and restricted to branch viewed.

Could be nice to improve search feature step by step :

with enable search zone on each repository
https://gitea.com/gitea/go-sdk vs https://gitea.com/gitea/go-sdk/commits/branch/master
add code search on repos explorer and return repository related
https://gitea.com/explore/repos
enable indexer feature on wiki, PR, issues, ....
enable all search option on repository page and respository explorer

Looks a very big work ....

@camlafit commented on GitHub (Jul 1, 2021): Hello Could be nice to provide a global search. If we following github behavior, we can do a search on : * repository name * code * commits * issues * wiki * users And some more (but doesn't looks) related to gitea features. https://github.com/search?q=gitea We can filter in a specific organization or repository. In gitlab we can obtain result on : * Projects * Issues * Merge requests * Milestones * Users https://gitlab.com/search?group_id=&nav_source=navbar&project_id=&repository_ref=&search=gitea&snippets=false If I've understood gitea indexer behavior we can do search on commit and code and search feature is only displayed on commits page and restricted to branch viewed. Could be nice to improve search feature step by step : * with enable search zone on each repository https://gitea.com/gitea/go-sdk vs https://gitea.com/gitea/go-sdk/commits/branch/master * add code search on repos explorer and return repository related https://gitea.com/explore/repos * enable indexer feature on wiki, PR, issues, .... * enable all search option on repository page and respository explorer Looks a very big work ....

GiteaMirror commented

2025-11-02 06:35:30 -06:00

@lunny commented on GitHub (Jul 2, 2021):

Issues and PR comments has been added indexer. I think we just want a global search page to aggregate all search features.

@lunny commented on GitHub (Jul 2, 2021): Issues and PR comments has been added indexer. I think we just want a global search page to aggregate all search features.

GiteaMirror commented

2025-11-02 06:35:30 -06:00

@thegitworker commented on GitHub (May 22, 2024):

Lacking a search on releases makes my use case a bit cumbersome.

I have one repository that can produce multiple software applications (i.e. it is essentially a kernel, and each application has config files where you can make each application using those config files). If you use the release section it quickly becomes unusable as a software that doesn't get updated frequently gets buried with no way to easily access it.

Example:

Software D released
Software C released
Software D released
Software B released
Software C released
Software B released
Software A released

You can see Software A gets buried. There is no way to search for it, filter it, sort it, etc. A search would suffice so I've added a comment here to this global search issue. If you believe this is better as a separate issue, I can create one for it.

@thegitworker commented on GitHub (May 22, 2024): Lacking a search on releases makes my use case a bit cumbersome. I have one repository that can produce multiple software applications (i.e. it is essentially a kernel, and each application has config files where you can make each application using those config files). If you use the release section it quickly becomes unusable as a software that doesn't get updated frequently gets buried with no way to easily access it. Example: - Software D released - Software C released - Software D released - Software B released - Software C released - Software B released - Software A released You can see Software A gets buried. There is no way to search for it, filter it, sort it, etc. A search would suffice so I've added a comment here to this global search issue. If you believe this is better as a separate issue, I can create one for it.

GiteaMirror commented

2025-11-02 06:35:30 -06:00

@lunny commented on GitHub (May 22, 2024):

I think this is unrelated, please create another issue.

@lunny commented on GitHub (May 22, 2024): I think this is unrelated, please create another issue.

GiteaMirror commented

2025-11-02 06:35:30 -06:00

@jowilkes commented on GitHub (May 22, 2024):

I think this is unrelated, please create another issue.

I think it is related (implementation may overlap), but still a different issue. - worth linking to from this one, once it exists.

@jowilkes commented on GitHub (May 22, 2024): > I think this is unrelated, please create another issue. I think it is related (implementation may overlap), but still a different issue. - worth linking to from this one, once it exists.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5773