From 585691b928badb00b335e41bf04df8928b6014bd Mon Sep 17 00:00:00 2001 From: Chiedo John <2156688+chiedo@users.noreply.github.com> Date: Wed, 16 Dec 2020 12:40:16 -0500 Subject: [PATCH 1/2] Make the repo sync stall check less aggressive (#17018) Co-authored-by: chiedo --- .github/workflows/repo-sync-stalls.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/repo-sync-stalls.yml b/.github/workflows/repo-sync-stalls.yml index 8b4f19ab20..bc946b9703 100644 --- a/.github/workflows/repo-sync-stalls.yml +++ b/.github/workflows/repo-sync-stalls.yml @@ -40,7 +40,7 @@ jobs: const timeDelta = Date.now() - Date.parse(pr.created_at); const minutesOpen = timeDelta / 1000 / 60; - if (minutesOpen > 30) { + if (minutesOpen > 180) { core.setFailed('Repo sync appears to be stalled') } }) From d34d41dcd18d7588889a29f279ac19244529670f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivan=20=C5=BDu=C5=BEak?= Date: Wed, 16 Dec 2020 19:04:09 +0100 Subject: [PATCH 2/2] Remove mention of GraphQL API rate limit increases for GHEC organizations (#17006) * Section on rate limits should not be nested within section on node limits since those are separate limits * Remove mention of GraphQL API rate limit increases for GHEC orgs Fixes https://github.com/github/docs-content/issues/3474 Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- content/graphql/overview/resource-limitations.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/content/graphql/overview/resource-limitations.md b/content/graphql/overview/resource-limitations.md index fd787403ac..636fee5b9c 100644 --- a/content/graphql/overview/resource-limitations.md +++ b/content/graphql/overview/resource-limitations.md @@ -125,7 +125,7 @@ These two examples show how to calculate the total nodes in a call. = 22,060 total nodes -### Rate limit +## Rate limit The GraphQL API v4 limit is different from the REST API v3's [rate limits](/rest/overview/resources-in-the-rest-api#rate-limiting). @@ -136,13 +136,7 @@ To accurately represent the server cost of a query, the GraphQL API v4 calculate * The formula uses the `first` and `last` arguments on a parent connection and its children to pre-calculate the potential load on GitHub's systems, such as MySQL, ElasticSearch, and Git. * Each new connection has its own point value. Points are combined with other points from the call into an overall rate limit score. -The GraphQL API v4 rate limit is **5,000 points per hour**. - -{% if currentVersion == "free-pro-team@latest" %} - -For {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_app %}s that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 points per hour. - -{% endif %} +The GraphQL API v4 rate limit is **5,000 points per hour**. Note that 5,000 points per hour is not the same as 5,000 calls per hour: the GraphQL API v4 and REST API v3 use different rate limits.