2 ms·
"testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now after I attempted to migrate it to a group namespace from my own p
by zaarn 9y ago
"testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now after I attempted to migrate it to a group namespace from my own profile.
Though I generally do like GitLab and favor Github alternatives over Github as I see it as a single point of failure for the FOSS community at this point.
- YorickPeterse 9y ago> "testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now > after I attempted to migrate it to a group namespace from my own profile. Have you created an issue for this on https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues?
- zaarn 9y agoYes I have, there was no response to it and it was recently closed, I believe.
- connorshea 9y agoCould you link the issue so we can look into it?
- tscs37 9y agoHi, I'm not OP but I've got myself into basically the same problem; https://gitlab.com/gitlab-com/support-forum/issues/2291 https://gitlab.com/gitlab-com/support-forum/issues/2291 I tried some various solutions via CURL to get the repository unstuck (basically rewriting the URL the request is sent to since the project settings page was pointing at the wrong repo) and it basically reports an empty repo on the target (which doesn't show up for me on my profile) and a 404 on the original (which does show up on my profile)