Changesets / Vercel Automation Issues

Currently we have a repo that is using changesets and the changesets/action to publish our packages.

One requirement we have in our repo is that commits need to be signed. To accomplish this we are signing the commits in our Github action so that the changesets/action can create a PR and push commits that can be merged. This is all working fine.

The issue comes when the Vercel preview deployments fail, and indicate

Git author must have access to the project on Vercel to create deployments

This seems to be failing because our bot account does not have access to the Vercel project. Is there any way around this? We are not able to give the bot account access to the Vercel project, so I am just curious what the best approach might be.

TLDR

Bot account is being used by the changesets/action to create a PR and push signed commits to our repo, the PR is not able to be merged because of the failing checks for the Vercel preview deployments. Seemingly this is because our bot account does not have access to the Vercel project.

Hey @steveg152! It should work if you include a --token on the deploy command. This guide shows an example:

Please give that a try and let me know if it works for you :pray:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.