I have a Next.js website set up using Codegen, and Vercel is linked to and listening for Main branch updates at Github repo to auto deploy.
It worked at one point previously, but today, when triggerring publish from the Plasmic editor to Github repo, the auto deploy to Vercel is failing with error: Vercel - Git author plasmicops must have access to the project on Vercel to create deployments.
I’m not sure what I did differently this time, maybe previously I pushed to Github from my local CLI and had different user attached/associated.
I believe this is because at point in the process the git author “plasmicops” is being used and Vercel is validating against that user. But I’m not sure if I’m supposed to invite that user to my Vercel team, or is there a way to change the git author in that auto deploy process?
I am a new Pro Account user to plasmic and very excited to ramp up quickly. I just set up Vercel to automatically deploy a preview when Plasmic makes a new commit to the dev branch. However, Vercel is saying the same thing @rocket_dev posted abve.
The Error message I get in Vercel is: The deployment XXXXXX with SHA XXXXXXXX is blocked due to insufficient permissions. The github user plasmicops is not part of the team.
In Vercel I can invite team members for $20 per month so a) this seems crazy that I would have to burn a monthly user to enable this and b) inviting a member is by email only…plasmicops is simply a bot.
Hi, this seems to be a new rule in Vercel integration with GitHub, I am not aware of a way to directly avoid it, one possible attempt is to use webhooks to request a new deploy after each publish in Plasmic Studio (References: Webhooks | Learn Plasmic , Creating & Triggering Deploy Hooks). Let me know if that works for you.
Hello all. In the event that this is helpful to others I am going to share the solution Vercel proposes. I have not implemented it yet, but it seems plausible. Essentially, Plasmic will commit to my dev branch, I will set up an automate process to merge dev with a new staging branch and then I will have vercel pickup changes to the staging branch for preview and whenever I do a merge from staging (or dev) to main, it will deploy to production.
Here is their message to me:
I understand that modifying metadata is not an option on the Plasmic side. In this case, the best approach would be to utilize GitHub Actions (or any other CI/CD). Since **plasmicops** commits changes to your repository, you can disconnect the GitHub connection from your Vercel account and set up preview and production pipelines directly in GitHub. This process should be relatively straightforward, and we have a detailed guide available to help you through it - How can I use GitHub Actions with Vercel?
