Here is the message where he found out what happened:

I didn’t receive any information about it but when creating a support ticket I was told my account has been flagged and I had to do some extra verification. I’ve created a support ticket now and will keep you posted. I’ll believe it’s nothing major though, I use 2FA everywhere, the last commit on all repos is what I expect, and all sessions and usages look fine

Absolutely fuck Github and Microslop, they can just vanish your projects without notice whenever they want with barely any justification for it, and then take their sweet time to fix it too.

  • vort3@lemmy.ml
    29·
    1 month ago

    Idk what is “kitchenowl”, but yesterday I had a situation where I need to create a github issue (well, I needed a software developer know about something, and the software is only hosted on github).

    I created a new github account, created an issue, logged out and saw that my issue isn’t there. Turns out my account was flagged. I tried to reach support, but github asks to enable 2FA for this. Added an authenticator.

    Turns out, you still can’t reach github support until you add and verify a phone number via SMS. No way I’m giving away my phone number to microsoft.

    So, it’s not possible to reach the support, there is no email address, and I can’t create issues. What a joke. I wish people in FOSS community stopped using github.

    In the end, I just found the dev’s email address and sent them an email.

  • Daniel Quinn@lemmy.caEnglish
    27·
    1 month ago

    What is it going to take to push FLOSS software out of GitHub? Everyone here can move their projects literally anywhere else today. I did it for my own (roughly 10 projects) five years ago and it only took about an hour:

    1. Create an account with Codeberg, GitLab, or whatever you like.
    2. Use their built-in tools to copy your repo over to your new account. In GitLab’s case, this will even migrate over some of the additional features, like issues.
    3. Update the places where you publish the project: PyPI, npm, whatever, with the new project home URL.
    4. Archive the old project on GitHub, with a pointing link to the new project home.
    5. (Optional) announce the above in any of the social spaces where people care about your project.
    • WhyJiffie@sh.itjust.worksEnglish
      6·
      1 month ago

      for anyone reading this, Codeberg/Forgejo can migrate issues too! use the “new migration” function in the menu where you create new repositories, and tick the box for copying issues and wiki. it is a one time copy only, though, so if you are dedicated you should restrict issues on the github repo to collaborators only, so that people can’t open new issues (which won’t be able to be synced anymore), but old ones are still readable in their original form.

      syncing issues cannot be done later, it’s for new repos only

  • Slashme@lemmy.world
    20·
    1 month ago

    That’s the cool thing about git. You can just create a blank codeberg repo and then do:

    git remote add codeberg <URL>
git push codeberg --mirror

    Of course, this won’t include issues and other GitHub specific stuff, but it’s much more robust than most other tools.

    If Linus had only ever created git, he’d still have his place high up in the programmer’s pantheon.

  • fluffy8192 [undecided, undecided]@hexbear.net
    1·
    1 month ago

    Moderators on Reddit and Lemmy do this kind of crap all the time though. It’s popularly considered to be right and normal. People defend the practice.

    I mean, it’s insane of course. But there you go. Big incongruity.