-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global Repo search #12302
Comments
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.
|
More a feature proposal issue about a "global search" like here on GitHub. (sorry, I didn't explain myself enough before) 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). |
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. |
Hello Could be nice to provide a global search.
And some more (but doesn't looks) related to gitea features. We can filter in a specific organization or repository. In gitlab we can obtain result on :
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 :
Looks a very big work .... |
Issues and PR comments has been added indexer. I think we just want a global search page to aggregate all search features. |
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:
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. |
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. |
[x]
): MySQLDescription
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:
The text was updated successfully, but these errors were encountered: