Help New repositories but i just want to connect to the original!

[HigherHeightsES]

🏷️ Discussion Type

Question

Body

Hi everyone — hoping someone here can help me untangle a repo issue.

I’m working on a website built with Loveable, which was originally connected to GitHub and then deployed through Netlify. After transferring the project to a different Loveable account, something odd started happening:

Loveable keeps creating new GitHub repos every time I reconnect it, instead of linking back to the original repo that has all the real commit history.

Right now I’ve ended up with one repo that has all the work, and several new empty ones that only show tiny recent edits. Changes I make in Loveable show in the editor, but they don’t show up on the live site anymore — I’m guessing because it’s pushing to the wrong repo.

Has anyone dealt with this before?
Is there a way to reconnect Loveable to the original repo without it generating a new one each time?

I’m still pretty new to GitHub, so any guidance would be massively appreciated. I just don’t want to lose months of work or break the live site while we’re actively updating it.

Thanks in advance!

[Gecko51]

This is a Loveable wiring problem more than a GitHub one, but the fix is on the GitHub side.

When you connected Loveable from the new account, it installed a fresh GitHub App on that account. That install only has access to the new (empty) repos it created. Your original repo still belongs to the old account, so Loveable on the new account can't see it and defaults to spawning a new one every time.

Two things to check:

1. Where does the original repo actually live? Go to https://github.com/[original-account] and confirm. If it's still under the old account, you'll need to either transfer the repo to the new account (repo Settings > General > Transfer ownership at the bottom), or give the new account collaborator access on the original repo.

2. On the new account, check the Loveable GitHub App permissions:

   • Go to https://github.com/settings/installations
   • Find the Loveable app, click Configure
   • Under "Repository access", add the original repo (or switch to "All repositories" if you're ok with that)

Once the App can actually see the original repo, Loveable's repo picker should list it and you can point the project at it instead of creating yet another one.

One more piece: the live site on Netlify is a separate wire. After Loveable is pointing at the right repo, go into Netlify and update the site's build source to that same repo. Otherwise Netlify is still watching the old repo and nothing you push will show up live.

Before doing any of this, clone the original repo to your local machine as a backup (git clone <repo-url>). If anything goes sideways during the reconnect, you've got every commit safe on disk.

If Loveable still creates a new repo after the App has access to the original one, that's worth pinging their support about. The usual GitHub integration flow is "pick existing", not "always create new".