78148dae50
* Updates * Update * Update * Update * Update * Yarn sometimes prefers npmrc, so use same token * Description * Update readme * Feedback * Add type * new toolkit and scoped registries * npmrc in RUNNER_TEMP * Dont always auth * Try exporting blank token * Get auth working for now pending runner changes * Fix string interpolation for auth token. * Don't export both userconfigs * Update authutil.js * Add single quotes for authString * Fix the registry string. * Use userconfig and append trailing slash * Keep in root of repo * Try just adding auth token * Remove auth token * Try changes again * Add tests * Npm and GPR samples * Add types
49 lines
943 B
Markdown
49 lines
943 B
Markdown
# `@actions/github`
|
|
|
|
> A hydrated Octokit client.
|
|
|
|
## Usage
|
|
|
|
Returns an [Octokit SDK] client. See https://octokit.github.io/rest.js for the API.
|
|
|
|
```
|
|
const github = require('@actions/github');
|
|
const core = require('@actions/core');
|
|
|
|
// This should be a token with access to your repository scoped in as a secret.
|
|
const myToken = core.getInput('myToken');
|
|
|
|
const octokit = new github.GitHub(myToken);
|
|
|
|
const pulls = await octokit.pulls.get({
|
|
owner: 'octokit',
|
|
repo: 'rest.js',
|
|
pull_number: 123,
|
|
mediaType: {
|
|
format: 'diff'
|
|
}
|
|
});
|
|
|
|
console.log(pulls);
|
|
```
|
|
|
|
You can also make GraphQL requests:
|
|
|
|
```
|
|
const result = await octokit.graphql(query, variables);
|
|
```
|
|
|
|
Finally, you can get the context of the current action:
|
|
|
|
```
|
|
const github = require('@actions/github');
|
|
|
|
const context = github.context;
|
|
|
|
const newIssue = await octokit.issues.create({
|
|
...context.repo,
|
|
title: 'New issue!',
|
|
body: 'Hello Universe!'
|
|
});
|
|
```
|