

Strange! Is it an issue with the setup or your woodpecker config file in the repo? Actioning on push is merely configuring steps after:
when:
- event: push
branch: main
Strange! Is it an issue with the setup or your woodpecker config file in the repo? Actioning on push is merely configuring steps after:
when:
- event: push
branch: main
I set up forgejo recently myself and ended up picking woodpecker. Lots of plugins available for standard stuff and relatively flexible. Docker config was easy and it spins up and shuts down docker containers to run the integrations, you can set up limits for number of concurrent jobs, things like that. You could see this as a plus or not, but woodpecker also has settings for secret management outside of the repo - global, repo-scoped, and user-scoped.
Recently been working on setting up forgejo to migrate away from GitHub. My open source stuff I’ve actually put onto codeberg and I’ve set up a handful of pull mirrors on my local instance for redundancy. This weekend I’ve been testing out woodpecker-ci for automating pushing files to s3 for some static websites for repos on codeberg as well as my forgejo instance. Today will tell if that is successful!
I’m in the process of setting up matrix / synapse for this case. Usability is yet to be determined because I need to recruit a sibling or two to test it out more, but I do have calls working on the element x app. Definitely not for the light hearted based on all the config options and possibility of federation.