Vercel Not Detecting New Branches After Git Repo Rename in Bitbucket

[jalalsordo-unocomau]

We recently renamed our Bitbucket repository. After the rename, Vercel stopped detecting branches—both existing (like develop) and newly created ones—and it no longer triggers any automatic builds or deployments. Previously, develop builds worked fine, but now even that fails to trigger.

Steps to Reproduce:

1. Have a Vercel project connected to a Bitbucket repository.
2. Rename the Bitbucket repository (e.g., from old-repo to new-repo).
3. Push updates or create a new branch in Bitbucket.
4. Check Vercel for automatic build and deployment.

Expected Behavior:

• Vercel should detect changes on the existing branches (develop, main, etc.).
• Vercel should automatically build and deploy for new branches as well.

Actual Behavior:

• Vercel no longer detects any branches (including develop) and does not trigger builds or deployments.

Troubleshooting Done So Far:

• We have tried re-verifying the repository within Vercel’s settings.
• We have confirmed that pushing to Bitbucket is successful and up-to-date.
• No errors or warnings appear in the Vercel dashboard regarding the repository connection.

Questions / Requests for Help:

• How can we re-link or refresh the connection in Vercel so that it recognizes our renamed Bitbucket repository?
• Are there any specific steps or known workarounds to get automatic builds/deployments working again after a repository rename?

Any guidance or suggestions from the community would be greatly appreciated! Thank you in advance.

[anshumanb (Anshuman Bhardwaj)]

Hi @jalalsordo-unocomau, welcome to the Vercel Community!

Sorry that you’re facing this issue. Also, kudos for sharing the context.

I see that you’ve arrived at a good solution with the idea to “re-link” the Git repository to your project.

You can do so by going to Project Settings > Git > Connected Git Repository:

After disconnecting the current repo, you can click on Bitbucket to re-link the repository with the updated name and that should fix the issue for you.

In the meantime, I’ll share this feedback with the product team to see if this flow can be improved.