-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add additionalPlugins parameter to getOctokit method #1181
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benwells
reviewed
Sep 21, 2022
benwells
reviewed
Sep 21, 2022
cory-miller
approved these changes
Sep 21, 2022
thboop
approved these changes
Sep 22, 2022
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.
lgtm
awendt
added a commit
to babbel/assign-to-repository-projects
that referenced
this pull request
Mar 11, 2024
We shouldn't have to do this: Using github.getOctokit from @github/actions directly instead of using its dependency, @octokit/core, would be preferable here. But it turns out getOctokit cannot be used with the paginateGraphql plugin, despite actions/toolkit#1181 (I couldn't get it to work).
awendt
added a commit
to babbel/assign-to-repository-projects
that referenced
this pull request
Mar 11, 2024
We shouldn't have to do this: Using github.getOctokit from @actions/github directly instead of using its dependency, @octokit/core, would be preferable here. But it turns out getOctokit cannot be used with the paginateGraphql plugin, despite actions/toolkit#1181 (I couldn't get it to work).
awendt
added a commit
to babbel/sync-repository-projects
that referenced
this pull request
Mar 14, 2024
We shouldn't have to do this: Using github.getOctokit from @actions/github directly instead of using its dependency, @octokit/core, would be preferable here. But it turns out getOctokit cannot be used with the paginateGraphql plugin, despite actions/toolkit#1181 (I couldn't get it to work).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows clients to configure their Octokit/Github instance with OctoKit plugins. This is a variadic parameter, so it should not break existing calls to
getOctokit