Connect timeouts and rate limit issues

• Extension version: Any
• VSCode Version: 1.112.0
• OS: macOS 15.7.3
• Repository Clone Configuration (single repository/fork of an upstream repository):
• GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): Github.com

When running the extension I frequently find it freezing or unresponsive when starting up. When checking the output logs of the extension I can see it's running either in connect timeouts or getting rate limited by Github. This seems like there's too much concurrent calls being made by the extension.

2026-03-30 09:25:15.269 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.270 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.270 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.271 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.272 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.272 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.273 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.276 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.277 [error] [RateLimit] API call count has exceeded 140 concurrent calls.
2026-03-30 09:25:15.277 [error] [RateLimit] API call count has exceeded 140 concurrent calls.

2026-03-30 09:26:30.164 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.165 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Unable to fetch PR: Error: Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 
2026-03-30 09:26:30.166 [error] [GitHubRepository+0] Error querying GraphQL API (PullRequest): Network error: request to https://api.github.com/graphql failed, reason: connect ETIMEDOUT 140.82.121.6:443. 

It's really frustrating to me. On the one hand the extension is really useful when it works properly, code navigation when reviewing from within your IDE is sublime. But the number of times the extension freezes or stops working after a new release makes it impossible to work with for me.

Steps to Reproduce:

1. Open VSCode
2. Try to load the extension

拡張機能の起動から始め、ログに記載された GitHubRepository GraphQL API の PullRequest リクエストを追跡します。記載されている VS Code の手順でフリーズを再現しながら、同時実行される呼び出し、レート制限エラー、接続タイムアウトを観察します。このシナリオで起動時に GitHub に過剰な負荷をかけず、拡張機能が応答しなくならなくなれば完了です。