Global allowlist for codesearch on projects #10245

New Issue

GiteaMirror · 2025-11-02T09:02:00-06:00

GiteaMirror commented

2025-11-02 09:02:00 -06:00

Originally created by @techknowlogick on GitHub (Feb 9, 2023).

Feature Description

Due to the size of code index not all repos should be indexed, an admin may wish to only allow certain repos (or namespaces to be indexed).

Perhaps a global setting such as CODESEARCH_ALLOWLIST: org/*, user/project,... and if a repo is not in that list then it wouldn't be indexed. This could later be extended to add options to disregard archived/forked repos, etc..

Screenshots

No response

Originally created by @techknowlogick on GitHub (Feb 9, 2023). ### Feature Description Due to the size of code index not all repos should be indexed, an admin may wish to only allow certain repos (or namespaces to be indexed). Perhaps a global setting such as `CODESEARCH_ALLOWLIST: org/*, user/project,...` and if a repo is not in that list then it wouldn't be indexed. This could later be extended to add options to disregard archived/forked repos, etc.. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:02:00 -06:00

GiteaMirror closed this issue

2025-11-02 09:02:00 -06:00

GiteaMirror commented

2025-11-02 09:02:01 -06:00

@brechtvl commented on GitHub (Feb 9, 2023):

For our use case at Blender I think we would want to disable it on all forks, and that would be enough. A specific list of repos is not something we would use probably, since keeping that up to date is not so convenient.

@brechtvl commented on GitHub (Feb 9, 2023): For our use case at Blender I think we would want to disable it on all forks, and that would be enough. A specific list of repos is not something we would use probably, since keeping that up to date is not so convenient.

GiteaMirror commented

2025-11-02 09:02:01 -06:00

@lunny commented on GitHub (Feb 10, 2023):

For our use case at Blender I think we would want to disable it on all forks, and that would be enough. A specific list of repos is not something we would use probably, since keeping that up to date is not so convenient.

I think just disabling fork repositories is an easier implementation than allowlist, but there are still mirrors and even users in fact could do a localhost fork and push but not from Gitea itself.

@lunny commented on GitHub (Feb 10, 2023): > For our use case at Blender I think we would want to disable it on all forks, and that would be enough. A specific list of repos is not something we would use probably, since keeping that up to date is not so convenient. I think just disabling fork repositories is an easier implementation than allowlist, but there are still mirrors and even users in fact could do a localhost fork and push but not from Gitea itself.

GiteaMirror commented

2025-11-02 09:02:01 -06:00

@techknowlogick commented on GitHub (Aug 15, 2025):

closing based on https://github.com/go-gitea/gitea/pull/23187

The options could be extended, I think that PR is sufficient enough for this issue.

@techknowlogick commented on GitHub (Aug 15, 2025): closing based on https://github.com/go-gitea/gitea/pull/23187 The options could be extended, I think that PR is sufficient enough for this issue.

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#10245