From 4c3f8f8e6880f296113fc5ad3c78df4c4f615691 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kamil=20Gw=C3=B3=C5=BAd=C5=BA?= Date: Thu, 25 Jun 2026 16:50:07 +0200 Subject: [PATCH] Drop unused rateLimit selection from MaxPullRequest query MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit MaxPullRequest is a very high-frequency change-detection poll, and its handler (_getMaxItem) only reads the latest PR number — it never consumes the rateLimit block. The only generic consumer (RateLogger.logRateLimit) already degrades gracefully when rateLimit is absent (it falls back to the ?? 5000 / ?? 1000 defaults and other queries still report it), so removing this top-level field from the hottest query has no functional impact. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- src/github/queriesShared.gql | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/github/queriesShared.gql b/src/github/queriesShared.gql index 478893e5cc..eb154dc5a1 100644 --- a/src/github/queriesShared.gql +++ b/src/github/queriesShared.gql @@ -991,9 +991,6 @@ query MaxPullRequest($owner: String!, $name: String!) { } } } - rateLimit { - ...RateLimit - } } query GetMilestones($owner: String!, $name: String!, $states: [MilestoneState!]!) {