Debian and GNOME announce plans to migrate communities to GitLab

Re:Debian and GNOME announce plans to migrate communities to... by zaarn on Wednesday November 15, 2017 @06:39AM (#15703064)

"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.

[ Parent | on HN ]

Re:Debian and GNOME announce plans to migrate communities to... by YorickPeterse on Wednesday November 15, 2017 @08:54AM (#15703691)

    > "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?

[ Parent | on HN ]

Re:Debian and GNOME announce plans to migrate communities to... by zaarn on Wednesday November 15, 2017 @10:17AM (#15704315)

Yes I have, there was no response to it and it was recently closed, I believe.

[ Parent | on HN ]

Re:Debian and GNOME announce plans to migrate communities to... by connorshea on Wednesday November 15, 2017 @01:37PM (#15706434)

Could you link the issue so we can look into it?

[ Parent | on HN ]

Re:Debian and GNOME announce plans to migrate communities to... by tscs37 on Saturday November 18, 2017 @09:15AM (#15729003)

Hi,

I'm not OP but I've got myself into basically the same problem; 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)

[ Parent | on HN ]