> including CI pipeline
You'll want to be cautious, because readme and promises are not software; they're attempting to squat on[1] nektos/act[2] which itself is the 20/80 of GitHub Actions
You'll almost certainly be happier using woodpecker[3] or some other "external" CI system so you don't have to hopes-and-prayers your CI system
1: https://code.forgejo.org/forgejo/act
2: https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... and https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#...
3: https://github.com/woodpecker-ci/woodpecker (Apache 2)
what do you mean by "squat on"?
They didn't attempt to build a GitHub Action implementation, they took a known broken one and attempted to duct tape it, so now it's the worst of both worlds: maybe theirs is somehow better, but because everyone in the world knows how terrible act is, they have to say "oh, we built in top of act, but we added some things, fixed others, broke something else, and who knows[1] but good luck to you, our beta testers"
Had act been a known working project, maybe it would have been worth the risk of forking it, or hitching their wagon to it, but to take a weekender project and attempt to build the entire CI system on top of it is insanity. Well, it would have been insanity in a world before having software that sometimes works and sometimes gaslights you became VCs shoveling money. So don't listen to me, I obviously just haven't gotten on the "maybe it works" train
1: https://forgejo.org/docs/latest/user/actions/#:~:text=used%2...