You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
There are 3 ways to add internal repos to an instance:
Add the repo by name
Use "repositoryQuery": ["public"]
Use "repositoryQuery": ["org:org-name is:internal"]
However, on instances with many, fluctuating repos and fluctuating orgs, none of these are feasible.
"public" uses GitHub's public repos endpoint, which does not return visibility or topics as part of the JSON result, making it impossible to tell which repos are actually internal and yielding inconsistent search results for repos with topics.
And having to add a new repo or a new org to code host connections every time is extremely tedious.
What we should be able to do instead is add a new "internal" option to the repositoryQuery special cases that iterates over the users orgs, and lists all the repos for each org using visibility=internal
There are 3 ways to add
internalrepos to an instance:"repositoryQuery": ["public"]"repositoryQuery": ["org:org-name is:internal"]However, on instances with many, fluctuating repos and fluctuating orgs, none of these are feasible.
"public"uses GitHub's public repos endpoint, which does not returnvisibilityortopicsas part of the JSON result, making it impossible to tell which repos are actually internal and yielding inconsistent search results for repos with topics.And having to add a new repo or a new org to code host connections every time is extremely tedious.
What we should be able to do instead is add a new
"internal"option to therepositoryQueryspecial cases that iterates over the users orgs, and lists all the repos for each org usingvisibility=internal