Looks like gitlab now requires account verification for new accounts in addition to email. Either phone number or credit card.

This applies both to accounts created with a working email or by logging in using your github account. You can’t even verify your email until you go through step 1.

I don’t know when this started, but at least for the last month or two judging from these posts in the forums.

Fun fact: I don’t even want to host on gitlab, I just wanted to report bugs in some projects. So I’m locked out.

  • kevincox
    361·
    1 year ago

    This really sucks for bug reporting. I don’t mind this at all for hosting as that cost notable resources (especially their free CI tier) and they can set their own terms, but I want people to be able to report bugs without any trouble. (Although if spam is an issue maybe projects could opt-in to requiring this verification to report bugs).

    A work-around is maybe the service desk feature allowing reporting bugs via email but this has issues for proper collaboration:

    1. The reporter’s email is shared.
    2. The issue is private by default.
    3. Can’t collaborate on an existing issue.

    Maybe I’ll just go back to mailing lists… Or GitHub has gotten better recently. But GitLab’s CI is so much better.

    • TauZero@mander.xyz
      14·
      1 year ago

      I want people to be able to report bugs without any trouble.

      Thank you for being aware! I’ve experienced this on github.com. I’ve tried to submit issues several times to open source projects, complete with proposed code to solve a bug, but github shadowbans my account 6 hours after creating it (because I use a VPN? a third-party email provider? do not provide a phone number? who knows). I can see the issue and pull request when logged in, but they only see a 404 on their project page even if I give them a direct link. I ended up sending them a screenshot of the issue page just to convince them this was even possible. Sad to hear gitlab does it even worse now by making phone mandatory.