Deployment bugged after moving Gitlab repository

I have been using pages over the past few months. Been a great experience so far! Just today I moved the Gitlab repositories the pages code is is hosted in to a new subgroup in our Gitlab organization. When I try to programatically create a new deployment, either through the REST API or a webhook, I get an error that the specified branch could not be found. The same error appears in the pages UI when attempting to change certain settings. I could probably fix this by deleting and recreating the respective Cloudflare pages, if possible, I would rather not though, since quite a few settings depend on those staying up. Is there a way to fix this issue without recreating the Cloudflare pages? To be clear, I don't know for certain moving the repositories caused the issue. Edit: Recreating one of the pages does fix the issue (bug?). I would prefer not recreating the other (more complexly configured) page as well. Has anyone here encountered this issue before and managed to find a workaround?
0 Replies
No replies yetBe the first to reply to this messageJoin