-
-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reintroduce octokit retry and throttling plugins #189
Conversation
Im now seeing ncc generate 3 additional files. I need to investigate why before merging
|
/* global host */ | ||
/* eslint-disable block-spacing, no-multi-spaces, brace-style, no-array-constructor, new-cap, no-use-before-define */ | ||
|
||
'use strict'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ncc is now generating these files and I don't know why
@softprops any update on this PR? It would be great to have this retry feature!! 🙏 |
const gh = getOctokit(config.github_token, { | ||
//new oktokit( | ||
const OctokitWithPlugins = Octokit.plugin(retry, throttling); | ||
const gh = new OctokitWithPlugins({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so cool! I didn't know! :)
With the last stream up updates came an upgrade to the
@actions/github
package which made it difficult to configure plugins as one normally would with octokit.This had the effect of disabling automatic retry behavior with now has become a feature request.
It would seem the community around these actions octokit integrations with actions has moving around and there's a suggestion here to avoid using
@actions/github
and use@octokit/action
instead. I don't have a personal preference so long as the result ends up playing nicer with the octokit ecosystem