@WoodpeckerCI my main reason is that - iirc - steps in woodpecker run in isolated containers, while actions run the entire job in one. This allows me to build an environment iteratively from reusable components.

Another reason is tighter integration, and that Actions are good enough for my needs.