Explain internal repositoryQuery#286
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| ### Hitting GitHub Search API rate limit with repositoryQuery | ||
| When Sourcegraph syncs repositories configured via `repositoryQuery`, it consumes GitHub API search rate limit, which is lower than the normal rate limit. The `affiliated`, `public` and `none` special values, however, trigger normal API requests instead of search API requests. | ||
| When Sourcegraph syncs repositories configured via `repositoryQuery`, it consumes GitHub API search rate limit, which is lower than the normal rate limit. The `affiliated`, `public`, and `none` special values, however, trigger normal API requests instead of search API requests. `internal` is also a special value that uses the GitHub Search API to list all internal repositories. |
There was a problem hiding this comment.
Would it be useful to show a couple example code-host configs demonstrating these special values?
There was a problem hiding this comment.
+1 to @matt's suggestion. If we can add one it will be great. :)
There was a problem hiding this comment.
So there is the configuration section right above this that has all of the options for a code host connection: https://sourcegraph.com/docs/admin/external_service/github#configuration
And then also, right below this there's already an example of where "repositoryQuery": ["affiliated"] is used.
I'm not sure if it makes sense to add another example here as well, since this trouble-shooting bit is regarding rate limits that are hit. Just added the bit about internal also using search quota here since it would also end up running into the rate limit issue.
Doc update for https://github.com/sourcegraph/sourcegraph/pull/62266