Create an update-endpoints script that will take the OpenAPI specification from @octokit/openapi, create/update a generated/rest-api-routes.js file, which would be an array of all REST API routes that GitHub supports
When sending a request, compare the given route to the known routes defined in generated/rest-api-routes.js. If the route is unknown, log a warning if the response is a 404.
No worries if that doesn't make sense @praneetloke, there is lots of inside knowledge behind how the automated updates work for the@octokit/* packages based updates to GitHub's OpenAPI specifications
follow up to https://github.com/octokit/request-action/issues/80#issuecomment-1003630140
The setup would work similar to how https://github.com/octokit/plugin-paginate-rest.js updates src/generated/paginating-endpoints.ts.
update-endpoints
script that will take the OpenAPI specification from@octokit/openapi
, create/update agenerated/rest-api-routes.js
file, which would be an array of all REST API routes that GitHub supportsgenerated/rest-api-routes.js
. If the route is unknown, log a warning if the response is a 404.No worries if that doesn't make sense @praneetloke, there is lots of inside knowledge behind how the automated updates work for the
@octokit/*
packages based updates to GitHub's OpenAPI specifications