-
Notifications
You must be signed in to change notification settings - Fork 54
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
Actor name is not vercel[bot]
#56
Comments
did you find a solution? |
I'm getting the same error here:
Did you find a workaround for this? |
I came by a similar problem, but after diving in further, at least for me, the problem was because I didn't give the workflow the required permissions to run. It seems that because I specified other permissions, by default, everything else is denied, so I had to manually add them back in. I needed to add this to my workflow file. permissions:
pull-requests: write
+ checks: read
+ contents: read
+ deployments: read Does that fix y'all's issues? |
Bump, I'm still seeing this and @RyanClementsHax's suggested workaround doesn't fix it 😕 |
Not sure if Vercel have changed how deployments work, but checking the GitHub deployment for a specific sha reveals that the
creator.login
field is set to my username, notvercel[bot]
.wait-for-vercel-preview/action.js
Line 329 in bfdff51
Is it important that the deployments are filtered by this username?
wait-for-vercel-preview/action.js
Lines 223 to 225 in bfdff51
The text was updated successfully, but these errors were encountered: