uuj8za

You do have to ask for permission. https://docs.codeberg.org/ci/

Asking permission involves creating an issue on the Codeberg-e.V./requests repo: https://codeberg.org/Codeberg-e.V./requests/issues/new?template=ISSUE_TEMPLATE%2FWoodpecker-CI.yaml

Here’s an example issue asking permission for CI: https://codeberg.org/Codeberg-e.V./requests/issues/1663

They get back to you fairly quickly. I think the main thing they check for is if your project is FOSS. They don’t seem very strict otherwise.

After you get permission, you can go to https://ci.codeberg.org/login to access CI.

You’ll also need to create a .woodpecker folder in your repo.

Woodpecker docs are here: https://woodpecker-ci.org/docs/usage/intro

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

takes deep breath

AHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA

Just switch to Codeberg already.

Why Forgejo Actions and not Woodpecker CI, isn’t Woodpecker on Codeberg more stable? Yes, absolutely, in fact the documentation for Forgejo Actions on Codeberg is out of date right now

Waah?

Forgejo Actions will just feel way more familiar coming from GitHub Actions. The UI and YAML syntax is almost identical, and the existing actions ecosystem mostly works as-is on Codeberg.

Ah, ok. I don’t care about that.

Setting up woodpecker.

It’s a little more nuanced than that.

I will gladly write my own small, half-assed framework that I 100% know, can reason about, can debug, and can extend to fit my requirements. I will gladly pass on a fat-assed, bloated framework with a million dependencies, where I only need a few features, and where if I need something that isn’t offered by the framework I have to submit a PR or add some janky-ass workaround.