Search an organization's repos #1296

Closed
opened 2025-11-02 03:55:55 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @svarlamov on GitHub (Nov 30, 2017).

Description

To date, I have not been able to find a way to search an organization's repositories (even if I am the owner and we have a ton of repos under the org). This is a bit annoying with a bunch of repos and it would be great to be able to search them (by name at least) same as on the user's profile page. What would this involve? I haven't looked to deep through the code on this, but I imagine it's probably just a front-end template fix?

Originally created by @svarlamov on GitHub (Nov 30, 2017). - Gitea version (or commit ref): dab2b35 - Can you reproduce the bug at https://try.gitea.io: Yes, on a user's page we have search and on an organization's page we have no search :cry: User example: https://try.gitea.io/geek1011 Org example: https://try.gitea.io/gitea ## Description To date, I have not been able to find a way to search an organization's repositories (even if I am the owner and we have a ton of repos under the org). This is a bit annoying with a bunch of repos and it would be great to be able to search them (by name at least) same as on the user's profile page. What would this involve? I haven't looked to deep through the code on this, but I imagine it's probably just a front-end template fix?
GiteaMirror added the type/feature label 2025-11-02 03:55:55 -06:00
Author
Owner

@techknowlogick commented on GitHub (Nov 30, 2017):

I feel your pain, I have a couple of orgs with >100 repos in them and I have to use the explore page to filter for the repos I need.

I'm looking into adding this now, but if I get sidetracked and someone wants to pick it up later I'll put my notes here.

It isn't just a front-end template fix, as I've added {{template "explore/search" .}} to right under where the "create new repo for org" button is on the org profile template (/templates/org/home.tmpl), and 1. it throws an error (<eq .SortType "newest...>: error calling eq: invalid type for comparison), and 2. if I remove the sort dropdown it shows the correct search box in the org home page, however when I enter anything and search it will just add what is needed to the URL, but won't filter the page.

So what is needed is: ensure the type of SortType is a string, has a default value of newest, and add the filtering ability to org home page route. Of course the search bar will also need to be added to the template.

@techknowlogick commented on GitHub (Nov 30, 2017): I feel your pain, I have a couple of orgs with >100 repos in them and I have to use the explore page to filter for the repos I need. I'm looking into adding this now, but if I get sidetracked and someone wants to pick it up later I'll put my notes here. It isn't just a front-end template fix, as I've added `{{template "explore/search" .}}` to right under where the "create new repo for org" button is on the org profile template (`/templates/org/home.tmpl`), and 1. it throws an error (`<eq .SortType "newest...>: error calling eq: invalid type for comparison`), and 2. if I remove the sort dropdown it shows the correct search box in the org home page, however when I enter anything and search it will just add what is needed to the URL, but won't filter the page. So what is needed is: ensure the type of SortType is a string, has a default value of newest, and add the filtering ability to org home page route. Of course the search bar will also need to be added to the template.
Author
Owner

@richmahn commented on GitHub (Jan 22, 2019):

@techknowlogick Looking into implementing this, both for my company and upstream Gitea. Are there any reasons you found this isn't doable, or just hasn't been interest?

@richmahn commented on GitHub (Jan 22, 2019): @techknowlogick Looking into implementing this, both for my company and upstream Gitea. Are there any reasons you found this isn't doable, or just hasn't been interest?
Author
Owner

@lafriks commented on GitHub (Jan 22, 2019):

@richmahn it was just that because of code refactoring that PRs had to be redo so it was closed but feel free to implement it in new PR

@lafriks commented on GitHub (Jan 22, 2019): @richmahn it was just that because of code refactoring that PRs had to be redo so it was closed but feel free to implement it in new PR
Author
Owner

@richmahn commented on GitHub (Jan 22, 2019):

@lafriks Ok, thanks. Will do.

@richmahn commented on GitHub (Jan 22, 2019): @lafriks Ok, thanks. Will do.
Author
Owner

@richmahn commented on GitHub (Jan 22, 2019):

So, signaling intent to work on this issue as well. Will add any notes to this comment like @techknowlogick did above:

  • Currently reviewing the previous PR that was closed to make sure I'm not missing anything needed for this to work.
@richmahn commented on GitHub (Jan 22, 2019): So, signaling intent to work on this issue as well. Will add any notes to this comment like @techknowlogick did above: * Currently reviewing the previous PR that was closed to make sure I'm not missing anything needed for this to work.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1296