I have a NextJS project that I’m deploying to Vercel. I had been steadily contributing and deploying happily for quite some time until today. The current issue that I’m having is that I’m using Github Copilot to address some of my issues. As I said, this was working just fine until recently I started getting issues saying that the Copilot email must have access to the project in order to create deployments.
Error: Git author ``+Copilot@users.noreply.github.com`` must have access to the team some-team’s projects on Vercel to create deployments.
Is it true that I’m going to have to upgrade to Pro just so that I can make use of Github’s Copilot?
This happens because Vercel checks the git commit author, and GitHub Copilot uses +Copilot@users.noreply.github.com, which isn’t recognized as a valid team member.
You can fix this by configuring Copilot to use your own email so commits are attributed to you, or by manually committing Copilot’s changes with your git config.
Upgrading to Pro (to add the Copilot email as a team member) is possible but usually unnecessary, just making sure commits come from your verified email should resolve it.
I cannot for the life of me find where I can update this in GitHub.
To be clear, the issue is when I create an issue in GitHub, assign it to Copilot and then try to merge the changes that the GitHub Copilot Agent made. These are not commits that are coming from my local machine. They’re commits that GitHubs Copilot Agent made on my behalf.
Create new issue
assign issue to Copilot
Copilot opens a draft PR with proposed changes to the issue