From 7efe10f0ab4d61a2502e1e7b839e3b581fee8866 Mon Sep 17 00:00:00 2001 From: de666En Date: Mon, 14 Apr 2025 09:47:37 +0300 Subject: [PATCH] f Update README.md --- node_modules/@octokit/plugin-paginate-rest/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node_modules/@octokit/plugin-paginate-rest/README.md b/node_modules/@octokit/plugin-paginate-rest/README.md index 5443892..f7a8b8f 100644 --- a/node_modules/@octokit/plugin-paginate-rest/README.md +++ b/node_modules/@octokit/plugin-paginate-rest/README.md @@ -179,7 +179,7 @@ The `compose*` methods work just like their `octokit.*` counterparts described a Most of GitHub's paginating REST API endpoints return an array, but there are a few exceptions which return an object with a key that includes the items array. For example: - [Search repositories](https://developer.github.com/v3/search/#example) (key `items`) -- [List check runs for a specific ref](https://developer.github.com/v3/checks/runs/#response-3) (key: `check_runs`) +- [List check runs for a specific ref](https://docs.github.com/v3/checks/runs/) (key: `check_runs`) - [List check suites for a specific ref](https://developer.github.com/v3/checks/suites/#response-1) (key: `check_suites`) - [List repositories](https://developer.github.com/v3/apps/installations/#list-repositories) for an installation (key: `repositories`) - [List installations for a user](https://developer.github.com/v3/apps/installations/#response-1) (key `installations`)