plugin-retry.js
                                
                                
                                
                                    plugin-retry.js copied to clipboard
                            
                            
                            
                        Octokit plugin for GitHub’s recommended request retries
### What happened? the @octokit/plugin-retry package is unable to handle calling the Github API endpoint to list CODEOWNERS errors (https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#list-codeowners-errors). Since the API endpoint by default is expected to return...
### Describe the need doNotRetry only supports checking on status code. This is not enough in some cases. For example, I have a flow where I create a new repository...
Resolves #ISSUE_NUMBER ---- ### Before the change? * There were no types for the plugin ### After the change? * Adds types for the plugin ### Pull request checklist -...
This removes existing `ts-ignore` annotations from `plugin-retry.js`. I did my best to use existing types from `@octokit/types` and `@octokit/core` instead of creating new types or interfaces in this project. I...
Resolves #ISSUE_NUMBER (_not applicable; issue does not exist_) ---- ## Behavior ### Before the change? * The plugin always performs retries using polynomial strategy (`RETRY_AFTER_BASE * (RETRY_COUNT + 1)^2`) ###...
Two bits - I was trying to set `RetryAfter` and failed to figure out how. I don't think its hard but something in the docs must be confusing me. I'm...
I had to rush the transition to TypeScript a little bit. Instead of setting the correct types everywhere, I've added a few `// @ts-ignore` statements: https://github.com/octokit/plugin-retry.js/search?q=%22%2F%2F+%40ts-ignore%22&unscoped_q=%22%2F%2F+%40ts-ignore%22 I'd love a pull...
I was recently implementing a feature in my application that would grab repository statistics from the `GET /repos/{owner}/{repo}/contributors` endpoint. The problem I ran into was that if statistics have not...
Just an idea for later :tm: We can check https://www.githubstatus.com/api/v2/status.json if the request went to https://api.github.com and the server responded with 500, that way we could provide better error messages...
[](https://renovatebot.com) This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use...