Filter repos by regex

[nihaals]

If you want to search across a large number of repos, the current options are:

• Filter by org
• Filter by repo (with a lot of ORs)

It would be nice if you could also use a regex, which would be especially useful if repo names follow a set format e.g. <team>-<service name>. For example, if you wanted to filter by a team, you could do repo:/^orgname\/teamname-/.

[rhaksw]

Yes, for example when searching across all of github for a domain name here, the repo "darkreader" shows up a lot. There is no way to exclude that from search results. I'd like to be able to say something like -repo:.*/darkreader

[melissachang]

+1. For my search, there are 50+ (and growing) relevant repos. It's too much work creating 50 ORs.

[GPHemsley-RELX]

My organization has 7.7k+ repos with 2.6k+ users, all doing different things. To help organize (and because we are migrating from GitLab, which has repo group hierarchy), my team's repos are named with a specific pattern. As soon as I want to look across more than one repo of mine, search becomes effectively unusable because I can't target a wildcard set of repos.

[Timmmy-nlb]

There are some news for this topic?
A better search will be very helpfull!

[brunopini]

I would +10 this if I could

[RONNCC]

Any updates perhaps?

[LiteBrite82]

Code search supports regular expressions to search for patterns in your code. You can use regular expressions in bare search terms as well as within many qualifiers, by surrounding the regex in slashes. GitHub Documentation.

Does this cover the specific functionality you are looking for?

[jfreeland]

No, that does not cover the specific functionality referred to in this thread.

If you're working in a large organization with many repositories and want to narrow your focus to a specific organization's repos, for instance, you might want to do something like /repo:hashcorp/sre-.*/ or /repo:hashicorp/(consul|terraform|vault)/ to exclude other repositories from being included in the results entirely. At present you would have to do repo:hashicorp/consul OR repo:hashicorp/terraform OR repo:hashicorp/vault, as an example, and when you're working with many repositories with a common prefix, it's rather cumbersome to try to do this by hand.

Take for example sourcegraph/sourcegraph#20389.

[RONNCC]

An example is we have a naming convention for repos in my company that prepends the business unit to it so i want to do

something like

filetype: python repo:"$orgname-.* " DatabaseWriter

[LiteBrite82]

@look
Do you have any kung-fu for this?

[look]

Unfortunately, no. We'd like to implement this but haven't been able to yet (fun fact, we started on it but ran into some subtle bugs).