

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





Been daily driving Arch on my laptops for the last 10 years. It’s been great. Getting the latest software has been especially handy for laptops, where the kernel sometimes needs time to catch up to the latest hardware.
I ran Guix for a few months when I had some extra time and I liked it, but it was very different and not all software I needed ran on it (or ran well). I ended up going back to Arch, but I brought Guix with me, as a package manager.
I also ended up trying Fedora for the first time (ok, I was unemployed) recently and was pleasantly surprised. Turns out Fedora is pretty close to how I configure Arch. And it’s got some extra polish that was neat. I ended up installing Fedora Silverblue for my parents 6-8 months ago and it’s been working out great for them.
Anyway, Arch has been my reliable companion for the last 10 years.