GitHub’s latest transparency report reveals that the company received 2,000 valid DMCA takedown notices last year, resulting in the removal of over 31,151 projects. Targeted repositories included copied code, but also pirate apps, IPTV playlists, and many Nintendo Switch emulators. Circumvention takedowns increased slightly, but GitHub notes that these continue to be heavily scrutinized.

  • Lime Buzz (fae/she)@beehaw.org
    link
    fedilink
    English
    arrow-up
    62
    ·
    1 day ago

    Hope developers start actually either self hosting forgejo or move to a platform that isn’t run by a hostile organisation with ties to ICE (Microsoft), like codeberg.

        • jatone@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          11 hours ago

          there is a nice CI/CD system that works locally and at cost hosted runners for personal plans. its very early stage. but i’ve been using it for my personal projects.

          it runs on a virtualization stack, and it can do things like github code spaces + ci/cd + model training. has built in code coverage/custom metrics.

          the code spaces bit doesnt work perfectly yet sadly (upstream issues) and mac support needs some improvements.

        • arisunz@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          22 hours ago

          couldn’t tell you, never used either.

          well, that’s not entirely true. i self host Forgejo and Woodpecker, which i think (might be wrong here, especially because Forgejo does have its own CI/CD now) is what Codeberg offers. anyway, it’s been OK for the automatic deployments of my little projects. pipeline configuration was flexible and straightforward enough to surprise me in a good way.

        • morbidcactus@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          21 hours ago

          Forgejo Documentation says they should be familiar to people who use github actions, they’re not the same but I found that when debugging some a few months back that github information was applicable, if that helps.