this post was submitted on 30 Mar 2026
317 points (100.0% liked)

Programming

26291 readers
568 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] mesamunefire@piefed.social 3 points 14 hours ago (1 children)

How did you get the CI working in codeberg? last time I checked, you had to get permission to do so(?). I would love to switch when I have time.

[โ€“] uuj8za@piefed.social 7 points 14 hours ago* (last edited 14 hours ago)

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