Copilot is now injecting ads into GitHub pull requests. It's a disaster.

You can start by moving your development workflows (pull requests, issue tracking, etc.) to something like codeberg. You can continue publishing your PyPI package from Github by just pushing your code from codeberg to Github.

Eventually you can also move the publishing pipeline over as well. I don’t know how complicated your library is, of course, but in simplest cases it’s a matter of rewriting a config file in a slightly different way.

I mean, if Zig and Guix can do it. It's possible.

I'm in a similar boat. So far:

• I started mirroring GitHub to Codeberg
• I added CI to Codeberg

Next I gotta update the readme on GitHub telling everyone that I'm going to move to Codeberg. I'll let that sit for a few months.

Also, I gotta update consumers like homebrew to consume from Codeberg instead.

I was gonna close/merge any open PRs on GitHub.

Issues, I'm not totally sure about. I thought I read there was a way to migrate those. Although, I'm kiiinda ok with starting fresh........ not totally sure this part needs more thought.

Once the Codeberg repo is ready, I'll make the GitHub repo read-only, with the readme pointing to Codeberg.

Way, way, way down the line, I'd consider deleting the GitHub repo (and finally my account).

I'm OK with breaking things. I'm gonna try my hardest to not break stuff, but I'm not going to let the fear of breaking stuff prevent me from getting on ShitHub by Macroslop.

# .woodpecker/my-first-workflow.yaml  
when:  
  - event: push  
    branch: main  

steps:  
  - name: build  
    image: debian  
    commands:  
      - echo "This is the build step"  
      - echo "binary-data-123" > executable  
  - name: a-test-step  
    image: golang:1.16  
    commands:  
      - echo "Testing ..."  
      - ./executable  

I think you would clone the repo and continue with codeberg. Announce wherever you can, and continue any new work at the new repo.

In case, you're not aware, you can also e-mail the dev. You can code up your commits as normal and then use e.g. git format-patch -3 to put the last 3 commits into patch files. You can then attach those files to an e-mail and the dev can apply those patches with git am.

It takes a bit of playing around, but it's actually really easy.
The Linux kernel, one of the most complex projects on the planet, develops like this.

Sourcehut duports git-email.

I currently have a GitHub account in order to contribute to projects hosted on GitHub, because I don't think there is currently a way possible to do thinks like open up an issue without an account.

Eventually it will be This feature can only be disabled on Enterprise or Pro+ plans

Yes, it was a Unicorn that Microslop bought.

Drink a verification can