"Error: Input required and not supplied: github-token"
See original GitHub issueAll of a sudden I’ve been getting this error.
/action/node_modules/@actions/core/lib/core.js:94
throw new Error(`Input required and not supplied: ${name}`);
^
Error: Input required and not supplied: github-token
at Object.getInput (/action/node_modules/@actions/core/lib/core.js:94:15)
at file:///action/index.js:28:15
at ModuleJob.run (node:internal/modules/esm/module_job:154:23)
at async Loader.import (node:internal/modules/esm/loader:166:24)
at async Object.loadESM (node:internal/process/esm_loader:68:5)
E.g. https://github.com/mdn/content/pull/2964/checks?check_run_id=2066177430
I haven’t touched my personal access tokens. And auto-merge hasn’t been upgraded on the project in 3 months. It just stopped working today all of a sudden. Sample PR: https://github.com/mdn/content/pull/2964
I don’t know if it’s a bug or user-error. Or a problem with GitHub Actions changing under our feet.
I did try generating a new access token (using the public_repo
scope) to see if that would make it work. But arguably, it’s a long shot because the error says the token isn’t supplied.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:15
- Comments:32 (11 by maintainers)
Top Results From Across the Web
error::Input required and not supplied: token · Issue #298
In summary, this error is expected if you are attempting to use a secret on a fork PR or a run triggered by...
Read more >Github actions Error: Input required and not supplied: task- ...
The problem is in the last step - Deploy Amazon ECS task definition. The problematic part is ${{ steps.task-def.outputs.task-definition ...
Read more >GH token not supplied - Development Tools - Project Nu
When it runs I get the following error: Error: Input required and not supplied: github-token Code: name: Add issue and PRs to project...
Read more >Top 5 @actions/github Code Examples
Use Snyk Code to scan source code in minutes - no build needed - and fix issues ... GitHub(inputs.token); // At this point...
Read more >GitHub Actions Security Best Practices [cheat sheet included]
In fact, it's probably better stated that there is no place where it's okay to do that, and CI workflow files are no...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I run into the same issue on a private repo. But after some time I realized the token needs to added to the
Depandabot
section instead ofActions
section which make it work for me.and it wasn’t just THIS action … seems like EVERY Personal Access Token wasn’t being read properly, here’s an example of a job that relies on a different PAT for usage with Github Package Registry:
upon re-running the job that also worked fine.
so … a global hiccup of all Personal Access Tokens (or all secrets) across Github!