I’ve completed all the steps recommend by the AI listed here (and more - I also blocked all access to all repos besides the non working one - that is currently linked, and vercel is still able to access the old repo which I blocked, which is the wrong one, which is concerning… ) with no change ::::
Even the UI in vercel deployment has the correct repo listed, but the actual link (on hover) is to the old (and blocked) repo - and that’s where it goes.
It seems like your deployment is still linked to the old repository despite your efforts to disconnect and reconnect the correct one. This issue might be caused by cached configurations or incorrect settings in your project.
Here are some steps you can take to resolve this:
- Verify the Repository Link in Vercel:
- Go to your Vercel dashboard.
- Navigate to the project settings and ensure that the correct repository is linked under the “Git” section.
- Check Environment Variables:
- Ensure that the
VERCEL_GIT_REPO_SLUGenvironment variable reflects the correct repository. You can find more details about this variable here.
- Clear Cached Configurations:
- Disconnect the project from the Git repository in the Vercel dashboard.
- Delete any
vercel.jsonfile in your repository that might still reference the old repository. - Reconnect the project to the correct repository.
- Redeploy Without Cache:
- Trigger a new deployment without using the existing build cache. You can do this by clicking the “Redeploy” button in the Vercel dashboard and unchecking the “Use existing Build Cache” option.
- Check GitHub Integration:
- If you are using GitHub, ensure that the Vercel app has the correct permissions for the new repository and that the old repository is no longer authorized.
If the issue persists after trying these steps, I recommend creating a support case so that the Vercel team can investigate further. Let me know if you’d like me to assist with creating a case.
I’m on a free plan so I could not create a support case as suggested, thanks in advance.