Skip to content
Latchkey

GitHub Actions "Input required and not supplied: github-token"

Some actions declare github-token as a required input with no default. If the workflow omits it (or passes an empty secret), the action fails immediately for a missing required input.

What this error means

An action fails at startup with "Input required and not supplied: github-token", even though GITHUB_TOKEN exists, because the action does not default to it.

github-actions
Error: Input required and not supplied: github-token

Common causes

Token input omitted

The action requires github-token explicitly and the with: block did not provide it.

Empty or undefined secret passed

github-token was set to a secret that is empty or undefined, which the action treats as not supplied.

How to fix it

Pass a valid github-token

  1. Add github-token to the action's with: block.
  2. Use secrets.GITHUB_TOKEN or a PAT with the needed scope.
  3. Confirm the referenced secret is actually populated.
.github/workflows/ci.yml
- uses: some-org/release-action@v1
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}

How to prevent it

  • Provide required inputs explicitly even when a token exists in env.
  • Verify secrets referenced for tokens are non-empty.
  • Read an action's required inputs before wiring it in.

Frequently asked questions

What causes ""Input required and not supplied: github-token""?
The action requires github-token explicitly and the with: block did not provide it.
How do I fix "Input required and not supplied: github-token"?
Pass a valid github-token

Related guides

References

Latchkey auto-heals failures like this one - detected, fixed, and retried without you. Start free → 30-day trial · No credit card