Skip to content

Conversation

@chrisgavin
Copy link
Contributor

@chrisgavin chrisgavin commented Sep 18, 2020

This will hopefully mean we get a newer version of Octokit and mean we can use Octokit plugins.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.

@chrisgavin chrisgavin force-pushed the update-actions-github branch from 86d2402 to 9ed519f Compare September 18, 2020 15:06
@chrisgavin chrisgavin marked this pull request as ready for review September 21, 2020 08:52
Copy link
Contributor

@robertbrignull robertbrignull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes to our code look behaviour preserving. However I'm confused why not update the use in api-client.ts to github.getOctokit as well? It would seem to be the intended entrypoint to the library. I think you'd need to move the auth parameter field to a parameter instead of being in the options object, but otherwise it's entirely equivalent.

@chrisgavin
Copy link
Contributor Author

That's a fair point. It feels like a slightly ugly interface but I agree it probably makes sense to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants