hi @drmarketing !
You can continue to use your repo in loader mode; disconnecting the repo is not an irreversible step – there should be no problems when reconnecting to the existing repo.
Can you send us some screenshots of what you see when trying to reconnect to GH?
Alternatively, you can continue to use your existing repo as-is and just connect the auto-deploy webhooks. In loader mode, we don’t push any component-related code, just the configuration code for the app, so you should be ok if you want your CI/CD to work on publish.
Here’s an example of how you can do it for vercel:
So when you say "There should be no problems when reconnecting to the existing repo.” I wonder if I approach this wrongly? How can I reconnect, facing the above?
Thank you for showing the “Webhooks only” alternative. Still, I would prefer to be able to reconnect to a repo. I am aware of this, but I produce several Vercel projects from one GitHub repo. Going via webhooks would turn quite messy and would not be the preferred route.
Besides, I just thought, “This must be somehow possible to reconnect a once disconnected repo.”
It would be great to learn the way to do so!
Looking forward to hearing your feedback. Thank you!