When using the Airbyte-managed GitHub connector, how are requests made to the GitHub API i.e is it one request per stream or per repository etc.?

Based on the provided knowledge sources, I don't have specific information about how requests are made to the GitHub API when using the Airbyte-managed GitHub connector in terms of requests per stream or per repository. The knowledge sources don't contain detailed information about the internal request structure of the GitHub connector. However, I can provide some relevant information about the GitHub connector's behavior: 1. The connector supports multiple streams, including issues, pull requests, commits, and others. Each stream likely requires separate API calls to retrieve its specific data. 2. The connector allows syncing data from multiple repositories or organizations, as mentioned in the [GitHub Source Setup Guide](https://docs.airbyte.com/integrations/sources/github#setup-guide). 3. The connector implements client-side throttling of requests to manage API rate limits, as noted in the [Config fields reference](https://docs.airbyte.com/integrations/sources/github#reference): "0.5.0 | 2023-05-16 | [25793](https://github.com/airbytehq/airbyte/pull/25793) | Implement client-side throttling of requests" 4. The connector handles rate limiting and provides options for load balancing across multiple API tokens: "To load balance your API quota consumption across multiple API tokens, input multiple tokens separated with

,

." Without more specific information from the connector's implementation details, I cannot provide a definitive answer about whether requests are made per stream, per repository, or in some other manner. If you need more detailed information about the request structure, you may want to consult the Airbyte documentation or reach out to Airbyte support for clarification.