Filter repos by regex #9824
-
If you want to search across a large number of repos, the current options are:
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. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 5 replies
-
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 |
Beta Was this translation helpful? Give feedback.
-
+1. For my search, there are 50+ (and growing) relevant repos. It's too much work creating 50 |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
There are some news for this topic? |
Beta Was this translation helpful? Give feedback.
-
I would +10 this if I could |
Beta Was this translation helpful? Give feedback.
-
Any updates perhaps? |
Beta Was this translation helpful? Give feedback.
-
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? |
Beta Was this translation helpful? Give feedback.
-
The feature is also helpful in situations such as finding a repository without specifying an organization. For example, if I want to search for all repositories whose name contains |
Beta Was this translation helpful? Give feedback.
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).