Negligent Pachinko Machine

    TypeScript icon, indicating that this package has built-in type declarations

    1.9.0 • Public • Published


    Core functions for setting results, logging, registering secrets and exporting variables across actions


    Import the package

    // javascript
    const core = require('@actions/core');
    // typescript
    import * as core from '@actions/core';


    Action inputs can be read with getInput which returns a string or getBooleanInput which parses a boolean based on the yaml 1.2 specification. If required set to be false, the input should have a default value in action.yml.

    Outputs can be set with setOutput which makes them available to be mapped into inputs of other actions to ensure they are decoupled.

    const myInput = core.getInput('inputName', { required: true });
    const myBooleanInput = core.getBooleanInput('booleanInputName', { required: true });
    const myMultilineInput = core.getMultilineInput('multilineInputName', { required: true });
    core.setOutput('outputKey', 'outputVal');

    Exporting variables

    Since each step runs in a separate process, you can use exportVariable to add it to this step and future steps environment blocks.

    core.exportVariable('envVar', 'Val');

    Setting a secret

    Setting a secret registers the secret with the runner to ensure it is masked in logs.


    PATH Manipulation

    To make a tool's path available in the path for the remainder of the job (without altering the machine or containers state), use addPath. The runner will prepend the path given to the jobs PATH.


    Exit codes

    You should use this library to set the failing exit code for your action. If status is not set and the script runs to completion, that will lead to a success.

    const core = require('@actions/core');
    try {
      // Do stuff
    catch (err) {
      // setFailed logs the message and sets a failing exit code
      core.setFailed(`Action failed with error ${err}`);

    Note that setNeutral is not yet implemented in actions V2 but equivalent functionality is being planned.


    Finally, this library provides some utilities for logging. Note that debug logging is hidden from the logs by default. This behavior can be toggled by enabling the Step Debug Logs.

    const core = require('@actions/core');
    const myInput = core.getInput('input');
    try {
      core.debug('Inside try block');
      if (!myInput) {
        core.warning('myInput was not set');
      if (core.isDebug()) {
        // curl -v
      } else {
        // curl
      // Do stuff'Output to the actions build log')
      core.notice('This is a message that will also emit an annotation')
    catch (err) {
      core.error(`Error ${err}, action may still succeed though`);

    This library can also wrap chunks of output in foldable groups.

    const core = require('@actions/core')
    // Manually wrap output
    core.startGroup('Do some function')
    // Wrap an asynchronous function call
    const result = await'Do something async', async () => {
      const response = await doSomeHTTPRequest()
      return response


    This library has 3 methods that will produce annotations.

    core.error('This is a bad error. This will also fail the build.')
    core.warning('Something went wrong, but it\'s not bad enough to fail the build.')
    core.notice('Something happened that you might want to know about.')

    These will surface to the UI in the Actions page and on Pull Requests. They look something like this:

    Annotations Image

    These annotations can also be attached to particular lines and columns of your source files to show exactly where a problem is occuring.

    These options are:

    export interface AnnotationProperties {
       * A title for the annotation.
      title?: string
       * The name of the file for which the annotation should be created.
      file?: string
       * The start line for the annotation.
      startLine?: number
       * The end line for the annotation. Defaults to `startLine` when `startLine` is provided.
      endLine?: number
       * The start column for the annotation. Cannot be sent when `startLine` and `endLine` are different values.
      startColumn?: number
       * The start column for the annotation. Cannot be sent when `startLine` and `endLine` are different values.
       * Defaults to `startColumn` when `startColumn` is provided.
      endColumn?: number

    Styling output

    Colored output is supported in the Action logs via standard ANSI escape codes. 3/4 bit, 8 bit and 24 bit colors are all supported.

    Foreground colors:

    // 3/4 bit'\u001b[35mThis foreground will be magenta')
    // 8 bit'\u001b[38;5;6mThis foreground will be cyan')
    // 24 bit'\u001b[38;2;255;0;0mThis foreground will be bright red')

    Background colors:

    // 3/4 bit'\u001b[43mThis background will be yellow');
    // 8 bit'\u001b[48;5;6mThis background will be cyan')
    // 24 bit'\u001b[48;2;255;0;0mThis background will be bright red')

    Special styles:'\u001b[1mBold text')'\u001b[3mItalic text')'\u001b[4mUnderlined text')

    ANSI escape codes can be combined with one another:'\u001b[31;46mRed foreground with a cyan background and \u001b[1mbold text at the end');

    Note: Escape codes reset at the start of each line'\u001b[35mThis foreground will be magenta')'This foreground will reset to the default')

    Manually typing escape codes can be a little difficult, but you can use third party modules such as ansi-styles.

    const style = require('ansi-styles');'#abcdef') + 'Hello world!')

    Action state

    You can use this library to save state and get state for sharing information between a given wrapper action:


    name: 'Wrapper action sample'
        default: 'GitHub'
      using: 'node12'
      main: 'main.js'
      post: 'cleanup.js'

    In action's main.js:

    const core = require('@actions/core');
    core.saveState("pidToKill", 12345);

    In action's cleanup.js:

    const core = require('@actions/core');
    var pid = core.getState("pidToKill");

    OIDC Token

    You can use these methods to interact with the GitHub OIDC provider and get a JWT ID token which would help to get access token from third party cloud providers.

    Method Name: getIDToken()


    audience : optional


    A JWT ID Token

    In action's main.ts:

    const core = require('@actions/core');
    async function getIDTokenAction(): Promise<void> {
       const audience = core.getInput('audience', {required: false})
       const id_token1 = await core.getIDToken()            // ID Token with default audience
       const id_token2 = await core.getIDToken(audience)    // ID token with custom audience
       // this id_token can be used to get access token from third party cloud providers

    In action's actions.yml:

    name: 'GetIDToken'
    description: 'Get ID token from Github OIDC provider'
        description: 'Audience for which the ID token is intended for'
        required: false
        description: 'ID token obtained from OIDC provider'
        description: 'ID token obtained from OIDC provider'
      using: 'node12'
      main: 'dist/index.js'

    Filesystem path helpers

    You can use these methods to manipulate file paths across operating systems.

    The toPosixPath function converts input paths to Posix-style (Linux) paths. The toWin32Path function converts input paths to Windows-style paths. These functions work independently of the underlying runner operating system.

    toPosixPath('\\foo\\bar') // => /foo/bar
    toWin32Path('/foo/bar') // => \foo\bar

    The toPlatformPath function converts input paths to the expected value on the runner's operating system.

    // On a Windows runner.
    toPlatformPath('/foo/bar') // => \foo\bar
    // On a Linux runner.
    toPlatformPath('\\foo\\bar') // => /foo/bar


    npm i @actions/core

    DownloadsWeekly Downloads






    Unpacked Size

    75.8 kB

    Total Files


    Last publish


    • chrispat
    • bryanmacfarlane
    • hross
    • thboop
    • konradpabjan