-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using PAT throws error "Input required and not supplied: github-token" #201
Comments
It is expected behavior. This behavior is explained in Github Docs.
If you need to pass the |
The So with:
This leads the next issue on how to allow this method to trigger workflows since the PR is treated as if it were coming from a forked repository. With |
Unless the document is wrong. Here is the use case for using the
This is discussed inside #134 and there is no plan for reverting back to a backing API design. |
@austins with v3 there is no way to trigger workflows as a result of a PR being automerged by the action. It's a compromise we accepted because it simplifies the architecture of the solution. In all honesty we realized it after the fact, but we're not planning to go back to the previous solution anyway. I believe v2 is probably still working, but it can stop working any time as we're not actively maintaining it. |
It appears that GitHub workflows can be sent Dependabot secrets since November 30, 2021. Mixed sources made it hard to confirm this. This lines up with the doc @climba03003 linked to. I've added the secrets that the workflow jobs need in the "Dependabot secrets" settings for the repo. I didn't have to modify the Thanks for the help, @climba03003, and the info, @simoneb! Closing this issue since it's not a bug with |
Prerequisites
fastify/github-action-merge-dependabot version
3.1.4
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
ubuntu-latest (currently ubuntu-20.04)
Description
Using a PAT for github-token throws an error and fails on initial PR job run.
A PAT is used instead of the GITHUB_TOKEN to allow deployment workflows to be triggered on the main branch by PRs merges. See: Triggering a workflow from a workflow.
Raw log from the failed job:
However, re-running failed jobs once gets it to succeed.
I'm not sure if this is another issue with GitHub Actions or with github-action-merge-dependabot.
Steps to Reproduce
The workflow is triggered by a
pull_request
event notworkflow_dispatch
.This is the job yml (source):
permissions:
config is not specified as it only applies to the GITHUB_TOKEN.Use a PAT with repo permissions saved as a repository secret.
Expected Behavior
Does not throw an error on the initial run when using a PAT instead of the GITHUB_TOKEN.
The text was updated successfully, but these errors were encountered: