action.yml

name: 'run-circleci-artifacts-redirector'
description: 'Create a direct artifact link upon CircleCI completion'
branding:
  icon: check
  color: blue
author: 'Eric Larson'
inputs:
  repo-token:
    description: 'The GITHUB_TOKEN secret'
    required: true
  artifact-path:
    description: 'Path to the CircleCI artifact'
    required: true
  circleci-jobs:
    description: 'Comma-separated list of CircleCI jobs to monitor (default is "build_docs,build,doc")'
    required: false
  api-token:
    description: 'CircleCI API token secret, only needed if the repository is private'
    required: false
  job-title:
    description: 'The name of the job, as it will render on the PR GUI (default is "<name of CI job> artifact)"'
    required: false
  domain:
    description: |
      The domain on which CircleCI artifacts are hosted. Defaults to
      output.circle-artifacts.com.

      Can, e.g., be set to use the Scientific Python CircleCI
      proxy (https://github.com/scientific-python/circleci-proxy),
      which addresses some routing issues.
    required: false
    default: 'output.circle-artifacts.com'
  post-pending:
    description: |
      Whether to post a "Waiting for CircleCI ..." status while the CircleCI
      job is still running. Set to 'false' to halve the number of statuses
      this action creates (and therefore the number of workflow runs the
      `on: status` trigger produces).
    required: false
    default: 'true'
  no-artifact-state:
    description: |
      What to post when the job uploaded no artifacts: 'failure' (red, the
      default), 'success' (green, linking to the CircleCI job) or 'skip' to
      post no status at all. Useful when a job that uploads nothing is an
      expected outcome, e.g. a '[skip circle]' commit.
    required: false
    default: 'failure'
outputs:
  url:
    description: 'The full redirect URL'
runs:
  using: 'node24'
  main: 'dist/index.js'