2019-07-29 17:09:32 +00:00
# `@actions/github`
> A hydrated Octokit client.
## Usage
2020-06-03 01:39:46 +00:00
Returns an authenticated Octokit client that follows the machine [proxy settings ](https://help.github.com/en/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners ) and correctly sets GHES base urls. See https://octokit.github.io/rest.js for the API.
2019-07-29 17:09:32 +00:00
2019-08-07 21:23:44 +00:00
```js
2019-07-29 17:09:32 +00:00
const github = require('@actions/github');
2019-07-31 20:19:47 +00:00
const core = require('@actions/core');
2019-07-29 17:09:32 +00:00
2019-09-25 02:27:50 +00:00
async function run() {
// This should be a token with access to your repository scoped in as a secret.
// The YML workflow will need to set myToken with the GitHub Secret Token
2019-10-14 14:59:46 +00:00
// myToken: ${{ secrets.GITHUB_TOKEN }}
2019-12-10 14:11:03 +00:00
// https://help.github.com/en/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token#about-the-github_token-secret
2019-09-25 02:27:50 +00:00
const myToken = core.getInput('myToken');
2020-06-03 01:39:46 +00:00
const octokit = github.getOctokit(token)
// You can also pass in additional options as a second parameter to getOctokit
// const octokit = github.getOctokit(myToken, {userAgent: "MyActionVersion1"});
2019-09-25 02:27:50 +00:00
const { data: pullRequest } = await octokit.pulls.get({
owner: 'octokit',
repo: 'rest.js',
pull_number: 123,
mediaType: {
format: 'diff'
}
});
console.log(pullRequest);
}
run();
2019-07-29 17:09:32 +00:00
```
2019-08-07 21:23:44 +00:00
You can also make GraphQL requests. See https://github.com/octokit/graphql.js for the API.
2019-07-29 17:09:32 +00:00
2019-08-07 21:23:44 +00:00
```js
2019-07-31 20:19:47 +00:00
const result = await octokit.graphql(query, variables);
2019-07-29 17:09:32 +00:00
```
Finally, you can get the context of the current action:
2019-08-07 21:23:44 +00:00
```js
2019-07-29 17:09:32 +00:00
const github = require('@actions/github');
2019-07-31 20:19:47 +00:00
const context = github.context;
2019-07-29 17:09:32 +00:00
const newIssue = await octokit.issues.create({
...context.repo,
title: 'New issue!',
body: 'Hello Universe!'
2019-07-31 20:19:47 +00:00
});
```
2020-01-22 16:53:39 +00:00
## Webhook payload typescript definitions
The npm module `@octokit/webhooks` provides type definitions for the response payloads. You can cast the payload to these types for better type information.
First, install the npm module `npm install @octokit/webhooks`
Then, assert the type based on the eventName
```ts
import * as core from '@actions/core'
import * as github from '@actions/github'
import * as Webhooks from '@octokit/webhooks'
if (github.context.eventName === 'push') {
const pushPayload = github.context.payload as Webhooks.WebhookPayloadPush
core.info(`The head commit is: ${pushPayload.head}`)
}
```
2020-06-03 01:39:46 +00:00
## Extending the Octokit instance
`@octokit/core` now supports the [plugin architecture ](https://github.com/octokit/core.js#plugins ). You can extend the GitHub instance using plugins.
For example, using the `@octokit/plugin-enterprise-server` you can now access enterprise admin apis on GHES instances.
```ts
import { GitHub, getOctokitOptions } from '@actions/github/lib/utils'
import { enterpriseServer220Admin } from '@octokit/plugin-enterprise-server'
const octokit = GitHub.plugin(enterpriseServer220Admin)
// or override some of the default values as well
// const octokit = GitHub.plugin(enterpriseServer220Admin).defaults({userAgent: "MyNewUserAgent"})
const myToken = core.getInput('myToken');
const myOctokit = new octokit(getOctokitOptions(token))
// Create a new user
myOctokit.enterpriseAdmin.createUser({
login: "testuser",
email: "testuser@test.com",
});
```